Changing the "fully qualified" table name to non-qualified?

[anders_gustafsson]

2020-08-28-13-49-01.jpg

Sometimes I find that Crystal changes the table-names to fully-qualified names, ie, not LP_ANSTALLNING which I have here, but rather yadadatabase.dbo.LP_ANSTALLNING and this makes Crystal try to pull data from elsewhere, even if I have connected to another database. Is there any easy way to change back?

[former_member11696 · Accepted solution]

Hi Anders,

I think it depends on the Database Client you are using because CR Dynamically generates the SQL based on the Client being used.

For all current versions of MS SQL Server always use the MS SQL Native 11 client. Manually update each report to use that client, ODBC or OLE DB.

Seems to be the most stable.

Don

[anders_gustafsson]

It si ODBC/SQL Server now, let me try ODBC/SQL Native and see if it helps.