M
MarianneZ
I read the thread about database code corruption and have sworn to mend my
ways, split the database, not edit during a break and backup more frequently.
What happened to me was the vba code disappeared. Months of work just gone. I
back up weekly, so it's really just a weeks' worth (and happily a 4 day
week), but still. I didn't think such a thing was possible, especially giving
my frequent decompiles and compactings. But not evidently frequent enough.
As part of my backup, I export all the code. So my first thought was to just
import the cls files. Seemed like a good idea. But I get an error that the
Module name is invalid. Access has added a 1 to the standard name, e.g,
Form_Input form1. Could it be because "Input form" is 2 words?
This question is really a comment and a warning to others. Read Allen
Browne's tips on avoiding corruption. Access 2007 seems to have an extremely
flaky development environment. I'm hoping that what others say is true, that
when the database goes into production mode, it will be much more robust.
Oh, and when adding features to the next version of Access, Microsoft should
make decompiling an option from within Access, not an obscure command line
option.
ways, split the database, not edit during a break and backup more frequently.
What happened to me was the vba code disappeared. Months of work just gone. I
back up weekly, so it's really just a weeks' worth (and happily a 4 day
week), but still. I didn't think such a thing was possible, especially giving
my frequent decompiles and compactings. But not evidently frequent enough.
As part of my backup, I export all the code. So my first thought was to just
import the cls files. Seemed like a good idea. But I get an error that the
Module name is invalid. Access has added a 1 to the standard name, e.g,
Form_Input form1. Could it be because "Input form" is 2 words?
This question is really a comment and a warning to others. Read Allen
Browne's tips on avoiding corruption. Access 2007 seems to have an extremely
flaky development environment. I'm hoping that what others say is true, that
when the database goes into production mode, it will be much more robust.
Oh, and when adding features to the next version of Access, Microsoft should
make decompiling an option from within Access, not an obscure command line
option.