The following properties specify the database object names:

• TADStoredProc: CatalogName, SchemaName, PackageName and StoredProcName;
• TADTable: CatalogName, SchemaName and TableName;
• TADBottomUpdateOptions: UpdateTableName;
• TADUpdateOptions: GeneratorName;
• TADAutoIncField: GeneratorName;
• etc

A name may be specified:

• without quotes and AnyDAC will normalize name;
• enclosed into quotes and AnyDAC will use it as is.

For example on Firebird with SQL dialect 3:

AnyDAC fully supports quoted object names, including different DBMS quoted characters. To write a quoted name in a SQL in a DBMS independent fashion use the {id <name>} syntax. For example: 

SELECT * FROM {id Order Details}

To force TADTable to quote field names set FormatOptions.QuoteIdentifiers to True. 

AnyDAC supports the full object names, which include the catalog and / or schema names. 

When you are using the design-time editors, like a TADStoredProc.StoredProcName combo box, Query Builder, etc., they will return the full object name. To avoid catalog and / or schema names in the full object name, use the MetaDefCatalog and MetaDefSchema connection definition parameters. For example: 

[MSSQL_Demo]
DriverID=MSSQL
...
MetaDefCatalog=Northwind
MetaDefSchema=dbo

When a short object name is specified to StoredProcName, TableName, etc, they will be expanded into the full object names, using the current catalog and / or schema names. To override or avoid usage of current catalog and / or schema names, use the MetaCurCatalog and MetaCurSchema connection definition parameters. For example: 

[MSSQL_Demo]
DriverID=MSSQL
...
MetaCurCatalog=*
MetaCurSchema=*

Additionally, at design-time you may force AnyDAC to return object names without catalog and/or schema. For that in IDE menu item AnyDAC -> Preferences ... unmark "Use full object names".

Executing Stored Procedure, Browsing Table, Common connection parameters