[AccessD] Access 2002 - Another way to lose your work

Hi Shamil,

Actually the code modules and forms were all in the same front end. I do
have a library of code routines, but the front end is using the MDE version.
Just another one of life's mysteries that Access throws at us. 

Lambert

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil
Salakhetdinov
Sent: Wednesday, September 24, 2008 5:50 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access 2002 - Another way to lose your work

<<<
I still cannot figure out why the one object (a form) got saved, and all the
other changes (to code modules) got blown away.
>>>
Hi Lambert,

My guess is that form belongs to your FE mdb, and modules were from library
mdb?

Since MS Access 2000 AFAIKR (for sue that wasn't the case for MS Access 97)
if you debug/trace/edit your library mdb VBA code and try to save it then
you in fact save nothing...

I always keep VBA code from mdb library modules copied and pasted and saved
manually in text code files and after I quit my debug session I do open text
files and copy over the code in VBA modules - well, I must say almost didn't
do that stupid work anymore as I'm mainly working with .NET - this "feature"
of getting VBA code from library MDB lost is one of the main "no-go" with
serious VBA code development anymore...

To workaround the issue effectively (as MS is very probably not going to fix
that issue as VBA team doesn't exist there anymore or exists just to support
existing features AFAIU) - to workaround the issue effectively it would be
useful to have a COM add-in to be called by hot-key from VBA window to save
current (-ly opened) modules' code into text files, and have additional
feature to replace code in modules (including class/forms/reports modules of
course) from saved in text files...

But beware! - when I did try to do something like that with MS Excel VBA
projects - I mean replacing code modules using text files - I did end up in
constant GPFing of MS Excel VBA projects - no workaround...

For MS Access VBA - it usually works well but still one can get their mdb
broken - always keep a back-up copy in safe place when you do (mass) replace
of code in your VBA modules...

--
Shamil