I am about to create a replica of a database that has a number of forms and a lot of VBA in the background. When I tried this previously it ruined my database (see below). Has anyone had a replica corrupt a database? Do you have any tips for avoiding this?
Any suggestions would be appreciated.
I created my first replica a few days ago, tested it, discovered a problem in some code and fixed the code in the original database. Suddenly every time I tried to save a change to a module I received an access violation error and Access shutdown. A search on Microsoft seemed to indicate that I had a corrupted VBA module and the only solution was to export the tables and queries into a new database and start over (forms, reports, macros and modules apparently could not be exported without an error). Fortunately this all happened in one day, I was able pull the database from a backup and lost very little information.
Any suggestions would be appreciated.
I created my first replica a few days ago, tested it, discovered a problem in some code and fixed the code in the original database. Suddenly every time I tried to save a change to a module I received an access violation error and Access shutdown. A search on Microsoft seemed to indicate that I had a corrupted VBA module and the only solution was to export the tables and queries into a new database and start over (forms, reports, macros and modules apparently could not be exported without an error). Fortunately this all happened in one day, I was able pull the database from a backup and lost very little information.
