The company i am working for has been using an Access database for purchasing and inventory. this has become to small/dangerous due to the number of records and frequent 'database needs repair' errors. I am trying to migrate the database to a sql server w/ access front end and am runing into problems with most of the VB proceedures that are built into the database. the most common at the moment is a 'Write Conflict' error saying someone else changed the record i am editing. i know this can't be the case becasue i am working on this in an isolated environment. I have traced it to a VB script that changes a field from 'Entering' to 'Pending' (text field) on the click of the 'new record' button. any ideas?
Access 2000/2003, SQL server 2000If you have more than one channel open to the database server (a second "session", basically) then that may well appear to be "another user."|||doesn't seem to be, in my tracing, the issue seems to be that VB doesn't know that I'm the person makeing the changes. It looks like the VB script starts when the form opens, checks the contents of the record to be worked on and when the button is clicked, finds the contents have changed.|||Please post the code involved.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment