Hello all, and thanks in advance for your time and advice!
Issue: Forms bounded to SELECT queries are placing the record in edit mode when a user makes a change, and no UPDATE query is required to update the data in the table. I would like to separate the processes and remain disconnected from the table except when these two queries are run. Is there any way to simply populate a form with data from a SELECT query, then run an UPDATE query after the form is updated?
Background: I am developing an Access 2003 database on Windows XP that is used by multiple users to track test parts. We have the occassional issue that two users update one part simultaneously. I would like to stay disconnected from the tables as much as possible to avoid problems. My plan was to populate a form using a SELECT query, allow the user to update the information on that form, then run some code to compare old values versus new values, and run an UPDATE query to make the needed changes.
Thanks! Let me know if you need more information and I'll try to post it.
Joe
Issue: Forms bounded to SELECT queries are placing the record in edit mode when a user makes a change, and no UPDATE query is required to update the data in the table. I would like to separate the processes and remain disconnected from the table except when these two queries are run. Is there any way to simply populate a form with data from a SELECT query, then run an UPDATE query after the form is updated?
Background: I am developing an Access 2003 database on Windows XP that is used by multiple users to track test parts. We have the occassional issue that two users update one part simultaneously. I would like to stay disconnected from the tables as much as possible to avoid problems. My plan was to populate a form using a SELECT query, allow the user to update the information on that form, then run some code to compare old values versus new values, and run an UPDATE query to make the needed changes.
Thanks! Let me know if you need more information and I'll try to post it.
Joe