Results 1 to 6 of 6
  1. #1
    New Lounger
    Join Date
    Sep 2002
    Posts
    3
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Access 2002, ODBC, IBM Client Access Express (2002)

    I have a user who links to a database on an AS/400 box for viewing and updating. Previous to his receiving Access 2002 he had Access 97 and was able to view and update the linked table without a problem. On his old system he had Windows 98 and Access 97. On his new system he has Windows 2000 and Access 2002. Since moving to the new system he can view the database, but he is not able to update it. I am providing an attachment with the error message he receives, but here's the meat of it. Dialog box reads: Title, "Microsoft Access"; Message, "ODBC--update on a linked table 'DEREKLIB_DEL_GRPS' failed. [IBM][Client Access Express ODBC Driver (32-bit)][DB2/400 SQL]SQL7008 - DEL_GRPS in DEREKLIB not valid for operation. (#-7008)." Any help would greatly appreciated.
    Attached Images Attached Images

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Access 2002, ODBC, IBM Client Access Express (2002)

    Is the client actually trying to update the AS/400 table from Access? It sounds like you need an updated ODBC driver for the AS/400 to work with Access 20002. You would get that from IBM, not Microsoft.
    Charlotte

  3. #3
    New Lounger
    Join Date
    Sep 2002
    Posts
    3
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Access 2002, ODBC, IBM Client Access Express (2002)

    It turns out IBM had changed a default driver setting between Client Access Express V3R2 and V5R1. Once we changed it back, it worked flawlessly. Thanks for your help.

  4. #4
    3 Star Lounger
    Join Date
    Mar 2001
    Location
    Minneapolis, Minnesota, USA
    Posts
    262
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Access 2002, ODBC, IBM Client Access Express (2002)

    "...and what setting would that be?", asks the man who just received the same message after having changed from V4R4 to V5R1.
    <font face="Comic Sans MS"><font color=blue>~Shane</font color=blue></font face=comic>

  5. #5
    New Lounger
    Join Date
    Sep 2002
    Posts
    3
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Access 2002, ODBC, IBM Client Access Express (2002)

    Under Administrative Tools, Data Sources, select the Client Access ODBC driver. Click on Configure. Select the Server tab. Click the Avanced button. On the Commit mode drop down, *change is likely selected, choose 'Commit Immediate (*None).' I don't completely understand the explanation, but it goes something like this: If the file the connection is run against is not journaled, then 'Commit Mode' should be set to 'Commit Immediate (*None).' The Commit Mode is a new default setting in V5R1 Client Access. Hope that helps.

  6. #6
    3 Star Lounger
    Join Date
    Mar 2001
    Location
    Minneapolis, Minnesota, USA
    Posts
    262
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Access 2002, ODBC, IBM Client Access Express (2002)

    You're a life saver -- literally! Great hordes of nasty people were about to descend upon me! Thanks again! <img src=/S/bravo.gif border=0 alt=bravo width=16 height=30>
    <font face="Comic Sans MS"><font color=blue>~Shane</font color=blue></font face=comic>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •