> For years we have been using Microsoft Access to transfer data
> to/from an AS400 using the Client Access ODBC connection. We are
[quoted text clipped - 8 lines]
>
> -Rob T.
Often that symptom only shows up when viewing the table datasheet directly
while forms, reports, and queries are not affected. In that case you can
simply ignore it since you shouldn't be doing anything with the table
datasheet anyway.
You would likely find that a passthrough query against the same table
displays fine.

Signature
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Rob T - 28 Nov 2005 18:50 GMT
I thought this might be the problem but I can't do any
updates/inserts/deletes to the tables. I get an error like this:
"ODBC-insert on a linked table 'IMDSLTB' failed. [IBM][Client Access
Express ODBC Driver(32-bit)][DB2/400 SQL]SQL7008 - IMDSLTB in AMFLIBT not
valid for operation. (#-7008)
I haven't found much out there about this. :-(
>> For years we have been using Microsoft Access to transfer data
>> to/from an AS400 using the Client Access ODBC connection. We are
[quoted text clipped - 16 lines]
> You would likely find that a passthrough query against the same table
> displays fine.
Rick Brandt - 28 Nov 2005 21:16 GMT
> I thought this might be the problem but I can't do any
> updates/inserts/deletes to the tables. I get an error like this:
[quoted text clipped - 4 lines]
>
> I haven't found much out there about this. :-(
That error is usually a journaling problem. If you have your ODBC set up to
use anything besides "Commit Immediate *NONE" for commit mode then the table
being updated has to be journaled on the AS400.
You will find this setting in the advanced options of the "Server" tab in
your ODBC setup.
I have also seen this caused by a bug in version 10.00.00.00 of the Client
Access driver.

Signature
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Rob T - 29 Nov 2005 20:55 GMT
Commit mode was the problem. I'm not sure how it got changed in the ODCB
setup. Perhaps one of the critical updates or something.
>> I thought this might be the problem but I can't do any
>> updates/inserts/deletes to the tables. I get an error like this:
[quoted text clipped - 14 lines]
> I have also seen this caused by a bug in version 10.00.00.00 of the Client
> Access driver.