Sharing MS-Access Databases, Efficiently?
codewizard asks: "Ours is a bank and we have a bunch of MS-Access databases(>50) which are being used by around 50 users around the globe on a daily basis. The set of databases are stored on a SAMBA share and each user accesses from the mapped drive.
As expected, sharing conflicts arise and multiple users are unable to access at the same time. So, we proposed having multiple folders on SAMBA each of which would have all the databases and the users logon script would determine where their mapped drive points to. This led to synchronisation issues (when a change is required in one of the master databases, we need to manually synchronise all other folders) and increase in storage size in SAMBA. Anyone have any other ideas on how you would have gone about sharing these MS-Access databases?"
Fucking breathtaking, innit. Made all the worse by being prefixed with "codewizard asks".
I write a blog now, you should be afraid.
In this case, "codewizard" is referring to the new Microsoft Access Code Wizard. Apparently, someone at the bank clicked on the "debug" button in the error message dialog they got when their Access database was locked. This, of course, launched the "codewizard" which promptly generated and submitted this Ask Slashdot post.
It could happen... right?
Seriously, I want to know. Because if it's MY bank, our relationship is over.
I mean, Access - come ON!