Forum post
Strange ODBC Error (ESS MS SQL Server)
Forum post posted October 22, 2010 by TJW15904, last edited February 9, 2012
594 Views, 24 Comments
Title:
Strange ODBC Error (ESS MS SQL Server)
Your post:
I've had no trouble adding MS SQL tables to my solution, but all of the sudden cannot add a particular table for some reason. A screen shot is attached. Weird dialog box and the same error shows up in the fields!
FM Server Advanced 11
SQL Server 2008 with SP 1 and a non-default server collation
Any help during this strange and stressful time would be met with great forum posting appreciation!
TJW
Screenshot:
Answer
TJW15904:
Thank you for your post.
I checked with a couple other Support Technicians, and none of us have seen this error message before. Since this only seems to be happening with this one table, there is something FileMaker Pro does not like about the table. Can you provide more information about the structure of the table? That is, how many fields? What are the field types? Length of the fields? etc.
According to the call notes from today, you tried this with a new FileMaker Pro file and received the same error message. Assuming the ESS file may be damaged, please create a new SQL table with the same field names and field types, add one record and try connecting to this new table from FileMaker Pro. If this still fails, try removing some of the fields from the new table and try again. I'm hoping this can be narrowed down further.
If you find the exact steps to reproduce the problem, please let me know and I'll make sure this gets reported and tested.
TSGal
FileMaker, Inc.
Be the first to like this
|
Sign in to "Like"
Out of interest, what is the name of the SQL table?
TS_Oz, FileMaker Inc.
Be the first to like this
|
Sign in to "Like"
@TS_Oz
The name of the SQL table is ControlExtraData
Be the first to like this
|
Sign in to "Like"
@TsGal
236 fields
Types: text, number, timestamp
Longest filed name looks to be 34 characters.
Thank you!
Be the first to like this
|
Sign in to "Like"
@TsGal
Did the one record new table with same fields, still no dice...
:(
Be the first to like this
|
Sign in to "Like"
TJW15904:
Thank you for the information.
When you have time, can you create a second table with half the fields and field types and try to connect. Since this problem is only occurring with this one file, I'm trying to narrow it down to either a field name, the table, FileMaker Pro, etc. If you can eventually create another table with all of the same fields and field types, and if the new table doesn't crash, then move your data from the old file to the new file.
TSGal
FileMaker, Inc.
Be the first to like this
|
Sign in to "Like"
TJW15904:
Your second post arrived as I was replying to your first post. Therefore, there is something about the field names that FileMaker Pro doesn't seem to like. Please check your Inbox for instructions where to send the field names and field types. I'll make sure our Testing department test this out.
TSGal
FileMaker, Inc.
Be the first to like this
|
Sign in to "Like"
@TsGal
Sent the info per your message to me.
Be the first to like this
|
Sign in to "Like"
TJW15904:
Our testers want to verify the OS FileMaker Server is on. Also, what driver version of MS SQL are you using?
TSGal
FileMaker, Inc.
Be the first to like this
|
Sign in to "Like"
@TSGal
Windows Server 2008 R2 Standard (64 BIT)
SQL Server Native Client 10.0 ... 2007.100.2531.00 (32 BIT as recommended on filemaker.com)
Be the first to like this
|
Sign in to "Like"