Access 2002 Corrupts Easily -MAKE BACKUP OF DEVELOPMENT DB EVERY DAY!

[LarryF]

Access 2002 is fairly unstable compared to Access 97 due
to buggy new features requiring drastic changes in the
development environment:
Editing subforms in place
VBA coding is performed in a different window/process
Datasheets can have subdatasheets and subforms
Pivot Tables and Views
The addition of projects (.adp) to work with SQL Server

Each time you work on code in the VB Editor window,
compile, save, and CLOSE the window. I created a new
("Standard") module in the VB Editor, saved it (it was
saved as "Module1", I was not offered an option to name
it), then switched to the Access window to rename that
module. As soon as I typed a new name, the database
completely fried and I lost hundreds of hours of work!

BE SURE TO BACKUP ALL FILES AFTER ANY MAJOR CHANGES OR AT
THE CLOSE OF THE WORK DAY!

 

[Kevin3NF]

Larry...I'm sorry you lost all that work, but I have to disagree with you
about Access 2002 corrupting easily. Mine hasn't yet, and I've
created/modified dozens of databases in AccessXP since it came out.

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm

 

[LarryF]

Kevin:
Thanks for your kind words of encouragement.
I've created over 40 databases from small to enterprise
since I began with Access v1.0. I've even used Access 97
with SQL SVR as a backend (the hard way). I use a lot of
tricks to provide an above-average interface for my
customers. I like the new features in 2000/2002. My
experience has been that when Microsoft makes dramatic
changes it takes a few versions to work out the bugs, and
a few of the bugs are fatal.
Until someone develops a program that can repair
corrupted objects in Access ("The repair process... does
not try to repair damaged forms, reports, macros, or
modules" - Microsoft Knowledgebase article # 283849), I
would strongly suggest you backup your work each day as
that article recommends.
Good Luck