Results 1 to 2 of 2
  1. #1
    Join Date
    Oct 2003
    Near D.C.

    Unanswered: Commit to a linked database

    We have a process that is extensive enough, that it locks down usage of the tables it is working on for the length of time it runs.

    Access 2007 linked tables to DB2 LUW 9.7 using ODBC.

    Is there any way to trigger a commit within DB2 from Access for a certain period within the whole process?
    So we don't have to wait until the end.

    I was pondering a Save command, as a step within the macro,
    or embedded within VBA.

    Haven't had the chance to try it out yet.
    But any input or methods from anyone else would be appreciated.

  2. #2
    Join Date
    Dec 2004
    Madison, WI
    Does the table have an autonumber type field (ie. identifier that is automatically incremented.)

    The only time I've heard about a table being locked extensively is on tables that don't have an autonumber type field. These types of tables usually require issuing a 'SaveRecord' type of command on the form (depending on how the form is designed).

    I always use an autonumber field in all my data tables (regardless if it's an MSAccess, SQL Server or any other backend db table) and have never had to use a 'SaveRecord' type of command on the form or in code.
    Last edited by pkstormy; 02-10-11 at 12:47.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

Posting Permissions

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