J
Janet Ciegler
Just read with interest a plan for rescuing a damaged database by
importing all modules & good records to a new empty database. Twice I
have destroyed a database by importing a table or a form from another
database, both on the same machine, composed with the same version of
Access. The first time it happened, the table was a simple list of 46
counties, states, and 2-letter abbreviations. The second time, it was a
form with VBA code. The importing went smoothly, but after that,
nothing worked. Is this normal? Anything that can be done about it?
This question now is just for future reference, as both times I rebuilt
the damaged database from scratch. TIA. Jan
importing all modules & good records to a new empty database. Twice I
have destroyed a database by importing a table or a form from another
database, both on the same machine, composed with the same version of
Access. The first time it happened, the table was a simple list of 46
counties, states, and 2-letter abbreviations. The second time, it was a
form with VBA code. The importing went smoothly, but after that,
nothing worked. Is this normal? Anything that can be done about it?
This question now is just for future reference, as both times I rebuilt
the damaged database from scratch. TIA. Jan