We have an access database with heavy VBA code in access 2007. This was originally developed in access 2003 and converted to access 2007.
This database resides on the network location. Recently whenever users try to access this application (especially remotely) and for some reason they get hanged or do not exit properly, the database gets corrupted and the VBA code gets completely wiped off. We are able to restore from the back up copies.
In order to avoid this situation, we thought of splitting the database on the network and save the front end version of the file with .accde extension. When this is done, the .accde version opens successfully only on the machine where we do the split database. On other machines it does not work.
Is it possible that there is something more that needs to be done during the split database or during saving it as .accde extension so that it works for other users also??
This database resides on the network location. Recently whenever users try to access this application (especially remotely) and for some reason they get hanged or do not exit properly, the database gets corrupted and the VBA code gets completely wiped off. We are able to restore from the back up copies.
In order to avoid this situation, we thought of splitting the database on the network and save the front end version of the file with .accde extension. When this is done, the .accde version opens successfully only on the machine where we do the split database. On other machines it does not work.
Is it possible that there is something more that needs to be done during the split database or during saving it as .accde extension so that it works for other users also??