Does this mean that the ODBC failed once and worked a second time (which might suggest a network issue at that moment, for example) or that the ODBC opened OK but you got the error.
The error looks like it is to do with an external data lookup table rather than the main database open - or is your model using a Report or database as the primary source and then ODBC for the external lookup into the database or something like that?
iirc most ODBC applications can produce log files for connectivity and error. Do they help the diagnosis at all?
I played with the ODBC a little more. This is my observations:
If the value does not match up with the field type, Monarch will give me the error message I mention in the above posting. For example, the company field is an alphanumeric field. Monarch will give me the error when the some records have values of digits, say, '14' in the field. I wonder if that is a bug in Monarch because I do not have this kind of issue when using ODBC with MS Access to get data from AS400 tables.
That sounds odd. Have you tried editing the field type to set it to alpha again in the model created and saving it then clsoing and re-opening the database?
I may be struggling to come up with any kind of ODBC connectiity to check this out but I will try to perform some more general database experiments.