RobertIngles
Technical User
I really don't know if there is a solution to this other than not doing it.
I recently started opening my Access DB (on a shared network drive) via VPN because I work from home so often.
It seems that pretty much every second time I open the DB, I get a message that the VB modules have been corrupted and that it can only be opened if the VBA project is deleted. Is it possible that when I close the DB remotely it is not closing properly on the shared drive?
Does anyone know if there is a solution for this? I try to make sure that I only leave the DB open for what I need and close it immediatly after because I am paranoid about my VPN disconnecting and leaving the DB in an unstable state however even when taking this precaution I am having problems.
The only solution I can think of is to go back to copying the DB to my HD before leaving work, working with it at home and then copying it back to the shared drive each morning. Not a very elegant solution as I end up with a folder full of re-named previous versions (I always copy the previous day's DB into an archive folder before reloading the one I worked on last evening.
Any information or suggestions would be appreciated!
Thanks
Robert
I recently started opening my Access DB (on a shared network drive) via VPN because I work from home so often.
It seems that pretty much every second time I open the DB, I get a message that the VB modules have been corrupted and that it can only be opened if the VBA project is deleted. Is it possible that when I close the DB remotely it is not closing properly on the shared drive?
Does anyone know if there is a solution for this? I try to make sure that I only leave the DB open for what I need and close it immediatly after because I am paranoid about my VPN disconnecting and leaving the DB in an unstable state however even when taking this precaution I am having problems.
The only solution I can think of is to go back to copying the DB to my HD before leaving work, working with it at home and then copying it back to the shared drive each morning. Not a very elegant solution as I end up with a folder full of re-named previous versions (I always copy the previous day's DB into an archive folder before reloading the one I worked on last evening.
Any information or suggestions would be appreciated!
Thanks
Robert