We're testing a product from a vendor that takes XML files and "shreds" them into a SQL Server 2000 database. I've linked an Access database to the SQL Server DB (since I find Access an easier and quicker tool to look at the 150 tables!)
Of the 150 tables, only one is giving me fits. I can succesfully link the table, but when I attempt to open the table through Access, I receive the following message:
ODBC--Call Failed
[Microsoft][ODBC SQL Server Driver][SQL Server] Invalid Column Name 'ColumnName''. (#207)
This error is repeated until it fills the entire message box replacing 'ColumnName' with whaterver the next field name is.
These column names are very long (some more than 80 characters) and I noticed that Access seems to have truncated the names when it linked them.
I just wanted to verify that this error is likely being caused by the excessively long field names in the SQL Server DB. Could using another driver help the situation? Thanks for the insight.
Of the 150 tables, only one is giving me fits. I can succesfully link the table, but when I attempt to open the table through Access, I receive the following message:
ODBC--Call Failed
[Microsoft][ODBC SQL Server Driver][SQL Server] Invalid Column Name 'ColumnName''. (#207)
This error is repeated until it fills the entire message box replacing 'ColumnName' with whaterver the next field name is.
These column names are very long (some more than 80 characters) and I noticed that Access seems to have truncated the names when it linked them.
I just wanted to verify that this error is likely being caused by the excessively long field names in the SQL Server DB. Could using another driver help the situation? Thanks for the insight.