For years we have been using Microsoft Access to transfer data to/from an
AS400 using the Client Access ODBC connection. We are now having problems
with the connections where the data looks garbled when you open a table, or
it will say #DELETED in the fields.

My theory is one of the Microsoft critical updates made a change to the
system, but am not sure. I have tried to reinstall Client Access and MDAC
with no success.

Any suggestions?

-Rob T.

Rob T wrote:
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.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

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. :-(

"Rick Brandt" <rickbrandt2 (AT) hotmail (DOT) com> wrote

Rob T wrote:
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.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

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.

"Rick Brandt" <rickbrandt2 (AT) hotmail (DOT) com> wrote