Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: TFDConnection fails to open table in a database with non standard name


This question is answered.


Permlink Replies: 2 - Last Post: Jul 5, 2017 10:55 AM Last Post By: Francisco Alvar... Threads: [ Previous | Next ]
Francisco Alvar...

Posts: 83
Registered: 11/10/06
TFDConnection fails to open table in a database with non standard name  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jul 4, 2017 2:11 PM
Hi all:
I'm trying to connect to a database (MS-SQL Server 2008) with a non standard name:
databaseName.bat
In the IDE, I can set the connection properties (TFDConnection's Connection Editor) and "it connects" but when I activate a TFDQuery I receive an error from SQL-Server engine about the server is not in sys.Servers...
At runtime, the same error raises.
If I use an ADO Connection no error raises and the table is active.
I surrounded the database name with [], '', and '''' without success.

Any suggestions to circumvent this problem without renaming the database and keep using the TFDConnection instead of switching to ADOConnection
Best Regards

Francisco Alvarado
Dmitry Arefiev

Posts: 1,406
Registered: 12/7/03
Re: TFDConnection fails to open table in a database with non standard name
Correct
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jul 4, 2017 10:38 PM   in response to: Francisco Alvar... in response to: Francisco Alvar...
This as a SQL Server limitation - SQLPrimaryKeys ODBC call does not support catalog names with '.' inside.
To resolve the issue exclude fiMeta from FetchOptions.Items.

--
With best regards,
Dmitry
Francisco Alvar...

Posts: 83
Registered: 11/10/06
Re: TFDConnection fails to open table in a database with non standard name  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Jul 5, 2017 10:55 AM   in response to: Dmitry Arefiev in response to: Dmitry Arefiev
Thank you Dmitry!
Dmitry Arefiev wrote:
This as a SQL Server limitation - SQLPrimaryKeys ODBC call does not support catalog names with '.' inside.
To resolve the issue exclude fiMeta from FetchOptions.Items.

--
With best regards,
Dmitry
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02