Synametrics Technologies

I'm using WinSQL as a diagnostic tool to work out some bugs between an MS SQL Server and a 4D SQL Server. I connect successfully to the 4D SQL data source using the Generic ODBC plug-in, and then notice WinSQL is having problems parsing the catalog. Specifically, the fields for one table will appear under another table. Some tables show a subset of fields from another table. Some tables are entirely correct. In addition, the location of the errors may change at each connection. If I quit WinSQL, then reconnect and fetch a new catalog, the field assignments are different than before (this is with catalog cacheing turned off), but still incorrect for many tables. It turns out that some of the same tables that have these problems are the ones that MS SQL Server is having trouble updating. So it could be a catalog/driver problem. My question is, would there be a way to use WinSQL to get a log of the cataloging process, so I can see what the 4D SQL Server is reporting as its catalog? I tried activating the ODBC trace feature but it's extremely lengthy and difficult to read. Is there a better way to troubleshoot the catalog?

The tables that are not cataloged correctly tend to inherit the field structure of the first table that is browsed in WinSQL. If I browse one "incorrect" table, then switch to another "incorrect" table, the second selected table will display the same field structure as the first selected table in WinSQL, which is obviously not true. This shifting of field structure only occurs for the tables that have been repeatedly found to be "incorrect".

I resolved this problem. My database wasn't designed originally for SQL, so the table & field naming did not adhere to SQL conventions. When WinSQL gets non-conforming catalog information, it does some pretty weird things. If the names are adjusted to conform to SQL, the problem goes away.