Access 2003, multiple users, FE on machines/BE on server
I've re-written a db to make it faster for the users, so that only the data for the Widgets they are responsible for is written to temp/local tables in the FE on their machine, then when they are done the data is written back to the tables in the BE on the server (if the users chooses to save their data). This is the best solution for this db.
Only one user at a time can be "using" that Widget's data (i.e. have it loaded to their machine). This is fine because typically each Widget is only managed by one person/user. For those Widgets which have more than one 'owner', they are aware of this process and are sort of used to it from using other company systems where only one person at a time can "check out" the data (this is in an engineering group).
So, user-wise, this is all good.
"Writing to the server" = deletes records pertaining to the current Widget from multiple tables; appends data for the current Widget from the user's machine to those tables.
My question is this: when writing back to the server, even though no two users will be writing the same Widget's data back to the tables in the BE, could there be conflicts of just simply WRITING to the same tables at the same time? If two users hit the SAVE button at the same time, so that Widget data is deleted from the server tables then the Widget data from their computers is appended to the tables at the same time, will there be conflicts? If so I can keep track of who's currently 'saving' their data and have the next person 'wait' (altho it is so little time they won't even notice they are waiting). I just don't want to have to write this code if i don't have to.
Thanks.
I've re-written a db to make it faster for the users, so that only the data for the Widgets they are responsible for is written to temp/local tables in the FE on their machine, then when they are done the data is written back to the tables in the BE on the server (if the users chooses to save their data). This is the best solution for this db.
Only one user at a time can be "using" that Widget's data (i.e. have it loaded to their machine). This is fine because typically each Widget is only managed by one person/user. For those Widgets which have more than one 'owner', they are aware of this process and are sort of used to it from using other company systems where only one person at a time can "check out" the data (this is in an engineering group).
So, user-wise, this is all good.
"Writing to the server" = deletes records pertaining to the current Widget from multiple tables; appends data for the current Widget from the user's machine to those tables.
My question is this: when writing back to the server, even though no two users will be writing the same Widget's data back to the tables in the BE, could there be conflicts of just simply WRITING to the same tables at the same time? If two users hit the SAVE button at the same time, so that Widget data is deleted from the server tables then the Widget data from their computers is appended to the tables at the same time, will there be conflicts? If so I can keep track of who's currently 'saving' their data and have the next person 'wait' (altho it is so little time they won't even notice they are waiting). I just don't want to have to write this code if i don't have to.
Thanks.
