Post reply

SQL needs dbSeeChanges?

  • March 5, 2008 at 10:59 am

    #184729

    Perhaps this is related to the problems I reported earlier. I am getting this error message

    You must use the dbSeeChanges option with OpenRecordset when accessing a SQL Server table that has an IDENTITY column.

    This is coming from code that was working well in Access. Do I have to change all of my openrecordsets to use the dbSeeChanges option?

    Jim

  • March 5, 2008 at 2:07 pm

    #785758

    Check this MS site out:

    http://support.microsoft.com/kb/208799

    The key may be at the end where it includes:

    " DAO 3.6 Object Library"

    Good Luck

  • March 5, 2008 at 2:52 pm

    #785786

    In short - yes. That's the right way to do it.

    ----------------------------------------------------------------------------------
    Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply