while thinking of multiple people working on a single database over the internet I wonder which are either the most common ways to handle unstable internet connections.
IMO it seems best to always keep track of the last update of a record so that if a user has disconnected while working on a record ,,, if the last update is identical to their local record of the last update of the record their changes (while disconnected) are applied otherwise they get some kind of message and/or view of changes that occurred since the last time they referenced the data. But my opinion isn't one from knowledgeable experience.
So I went through all that just to ask,
1. Does mysql or sql server do this automatically?? If not, what happens and how can you control-manipulate the event/error??
2. When you link internet server back-end tables to access data projects can you call/use mysql or sql stored procedures with access's vba or is this question irrelevant, why?
3. I read somewhere that access vba has transaction commit functions , but, if you have mysql or sql as a back-end would you even have to bother??
IMO it seems best to always keep track of the last update of a record so that if a user has disconnected while working on a record ,,, if the last update is identical to their local record of the last update of the record their changes (while disconnected) are applied otherwise they get some kind of message and/or view of changes that occurred since the last time they referenced the data. But my opinion isn't one from knowledgeable experience.
So I went through all that just to ask,
1. Does mysql or sql server do this automatically?? If not, what happens and how can you control-manipulate the event/error??
2. When you link internet server back-end tables to access data projects can you call/use mysql or sql stored procedures with access's vba or is this question irrelevant, why?
3. I read somewhere that access vba has transaction commit functions , but, if you have mysql or sql as a back-end would you even have to bother??
