Dan Waters
df.waters at comcast.net
Tue Aug 9 08:13:41 CDT 2011
I've had this issue with 2003 as well. Just by trying to watch for a pattern, it looks like it happens if I'm stepping through code and make a change, then later on an error happens, and I didn't save in between. I still make changes while stepping through code, but I make a strict practice of saving, then compiling, after each and every change. Since then, the number of issues of non-saving has dropped significantly. One thing I've done to make compiling easier is to customize the standard toolbar by adding a compile button. Quicker and more visible than Debug | Compile. Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins Sent: Tuesday, August 09, 2011 5:02 AM To: accessd at databaseadvisors.com Subject: [AccessD] Access 2007 Failure to save design and code module changes. GRRRR!! What is it with A2007?? A quick google seems to suggest that others have had similar issues, although no one seems to have a solution. Has anyone else experience this? You make changes in the VBE or a form or form code and save (and save and save). But the changes are just dropped - nothing is saved. In this instance none of the usual possible reason given on google (database locked by other users, no write permission on the folder blah blah are relevant). It is one of the most *ANNOYING* bits of software I have had to misfortune to use. Anyone got any advice. I can't wait be done with it and move to A2010. cheers Darryl