[AccessD] Loss of Access 2007 Code Changes

Hi Max,

I've been seeing this for years in Access 2003.  About 2003, I met a guy at
a trade show who was switching to VB.Net back then.  He told me that Access
'goes backward'.  At the time I brushed that off, attributing his 'put down'
of Access to his decision to move to VB.  I wished that I had asked for more
info at that time.

I think that the problem is related to changing code while you are stepping
through it, then closing the database before you compiled and saved the
changes.  I've been trying to remember to not change code until it's out of
break mode, and also to compile and save immediately after a code change.

This has been very hard to 'get my hands around' - I couldn't prove to my
self that it wasn't me doing something wrong.  It's really frustrating, and
some of these lost changes have made it into my customers systems, which is
frustrating for them.  But a few weeks ago I had saved a copy of a database,
which later on I found had the changes I made, while the original database
did not.

So my suggestion is to stop recoding in break mode, and compile and save
very frequently.  

To help compiling quickly, you should customize the Standard toolbar by
adding a Compile button.  I put it just to the right of the properties
button since I'm there all the time anyway.

Good Luck!
Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Wednesday, March 17, 2010 5:59 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Loss of Access 2007 Code Changes


More problems at Mill...



Helen Feddema just reported this in the latest edition of her Access Watch
newsletter.

Loss of Access 2007 Code Changes
Recently, I have heard reports of code changes being lost in Access 2007
(and I have experienced it myself several times, especially when
transferring databases to and from clients).  It is a specific type of loss,
where after making changes to database code, saving the code and closing the
database, then the next time the database is opened the last saved change
has been undone.  If you made a backup of the database immediately after
making the change, usually the backup database does have the last code
change, so you can restore it.  Or you may have saved your code to a text
file or Word document, and then you can restore it from that document.

What is going on with A2k7?  

Max

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com