AS/400 connection problems "Rob T" <RTorcellini[ at ]DONTwalchemSPAM.com> 28.11.2005 16:27:36 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.

Re: AS/400 connection problems "Rick Brandt" <rickbrandt2[ at ]hotmail.com> 28.11.2005 17:20:33 Rob T wrote: [Quoted Text] > 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. 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

Re: AS/400 connection problems "Rob T" <RTorcellini[ at ]DONTwalchemSPAM.com> 28.11.2005 18:50:11 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.com> wrote in message news:B%Gif.20977$7h7.2125[ at ]newssvr21.news.prodigy.com... [Quoted Text] > Rob T wrote: >> 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. > > 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 >

Re: AS/400 connection problems "Rick Brandt" <rickbrandt2[ at ]hotmail.com> 28.11.2005 21:16:41 Rob T wrote: [Quoted Text] > 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. :-( 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

Re: AS/400 connection problems "Rob T" <RTorcellini[ at ]DONTwalchemSPAM.com> 29.11.2005 20:55:55 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.com> wrote in message news:ZsKif.18898$D13.6919[ at ]newssvr11.news.prodigy.com... [Quoted Text] > Rob T wrote: >> 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. :-( > > 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 >