cravincreeks
Technical User
We're about to launch some database programming projects in Access. But I'm thinking about suggesting to the boss that we use MySQL as the back end storage. The main reason I want to move away from Access is the lack of transaction logs and restoring a database to a particular place in time. For example, if somebody accidentally deletes a bunch of records or corrupts an entire field, then it is not possible to undo this tranaction in Access...am I correct? If there was a backup of the actual .mdb file, then we could pull that out and start over. But what if a lot of data have been written/updated/deleted since the last back up? All the new data are lost. So with MySQL, is it possible to restore a database to a certain place in time using the transaction log? I.e., can we search the transaction log for the bad transaction and restore it to the state it was in just before that particular transactions?
I also want to know one other thing about MySQL transaction logs and restoration. Say we have a bad tranaction where a user totally corrupts an entire and very important field. But this corruption goes unnoticed for weeks. Somebody finally notices the corruption and goes searching for the transaction that caused it. The bad transaction is found. But what happens to all of the valid transactions that have occurred after it? If we undo the bad transaction, are all of the subsequent transactions 'undone' as well? Or is it possible to only undo the bad transaction and keep the subsequent transaction?
If we go with MySQL, then most of the programming will be done using ADO and VB (6 and VBA). Is there anything I should know about using Access as a front end for MySQL?
Thanks for any help you can provide!
Alex
I also want to know one other thing about MySQL transaction logs and restoration. Say we have a bad tranaction where a user totally corrupts an entire and very important field. But this corruption goes unnoticed for weeks. Somebody finally notices the corruption and goes searching for the transaction that caused it. The bad transaction is found. But what happens to all of the valid transactions that have occurred after it? If we undo the bad transaction, are all of the subsequent transactions 'undone' as well? Or is it possible to only undo the bad transaction and keep the subsequent transaction?
If we go with MySQL, then most of the programming will be done using ADO and VB (6 and VBA). Is there anything I should know about using Access as a front end for MySQL?
Thanks for any help you can provide!
Alex