[AccessD] Access 2007 Failure to save design and code module changes.

Darren - Active Billing darren at activebilling.com.au
Tue Aug 9 19:10:22 CDT 2011


Dazza
I feel your pain brother, I really do.
First because of the weirdness - How is this a sellable product? I just
don't get it.
And also because you have to work in Acc200X -I find developing in either
2007 or 2010 is a real PITA.
On my main machine here I have 2010 but other machines in the office have
2003.
Now I develop on the other machines after the team has gone home for the
day.
What a PITA.

See ya


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins
Sent: Wednesday, 10 August 2011 9:38 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access 2007 Failure to save design and code module
changes.

Thanks Darren,

Luckily I was only sitting at my own desk working on a project and not
showing a client.  That would be really awful.  And yeah, I got lucky as I
am really old school so I tend to zip up a copy of the database I am working
on every couple of hours (or less) as a backup - Too many times have I had
Access get corrupt and been saved by a backup version so it is pretty much
habit now.

Now, Here is where it gets odd.  The last zip back up of the database I was
working on has the changes, but in the latest version of the database they
are all missing.  How the hell can that happen??  It is not like I have even
taken a copy and mixed up which version I was working on.  The zip is just a
zipped up version of the current database taken a bit back in time.  

Now i am going to have to compare the last zipped backup with the current
version and try to bolt the changes together, or at least recall what the
changes that have been dropped were.  Bah.

Cheers
Darryl.



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darren - Active
Billing
Sent: Tuesday, 9 August 2011 11:01 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access 2007 Failure to save design and code module
changes.

Hey Dazza from another Mother

Yes - I've had this - No, sorry, I don't have a solution for you. 
The first time I encountered this 'anomaly' was actually at a client's
office, whilst deploying (what I thought was) their new version.
The modified screens I had ploughed about 16 hours into over (what I thought
was) a very productive weekend, were just not there -Just not there. Yet
some 'new work' was.
I just assumed I had grabbed a backup made 'during' the process of the
modifications. And explained it as such to the client.
Then when I got back to the office the 'latest' version did not have my new
work changes either. Despite the Last modified date being 'about right'.
I could not work out what I had done. I was furious. And yes I saw some
mention of this stuff on the googaweb.

I'm not sure where the issue lies. I have a feeling (not confirmed) it's to
do with this new Vista and Win 7 file save feature.
The one that asks the following when you copy a file with the same name to
the same location...
"There is already a file with the same name in this location" 
Then you have the options of:  'Move and Replace' or 'Don't Move' or 'Move,
but keep both files'

So now, I work on a 'copy' of the real dB. I rename the copied dB, with the
new work with some silly name - Once complete I close all my work.
Then I open this new silly name dB, to make sure it actually has in it the
new or modified bits and pieces (tables, forms etc.) And only then do I
rename this new one back to the original name it should be as per the
client's version.
And even then I copy it and then put a copy on my dongle.
Then open the version on the dongle before I go to Client's to make
absolutely sure that the dongle version is indeed the correct version.

BTW - This happened to me a few times before I actually clicked that it
wasn't me (At least, I hope it wasn't me).

Sorry not much help - good luck.

D

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins
Sent: Tuesday, 9 August 2011 8:02 PM
To: accessd at databaseadvisors.com
Subject: [AccessD] Access 2007 Failure to save design and code module
changes.


____________________________________________________________________________
___________

Note: This e-mail is subject to the disclaimer contained at the bottom of
this message.
____________________________________________________________________________
___________


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
____________________________________________________________________________
___________

The information transmitted in this message and its attachments (if any) is
intended only for the person or entity to which it is addressed.
The message may contain confidential and/or privileged material. Any review,
retransmission, dissemination or other use of, or taking of any action in
reliance upon this information, by persons or entities other than the
intended recipient is prohibited.

If you have received this in error, please contact the sender and delete
this e-mail and associated material from any computer.

The intended recipient of this e-mail may only use, reproduce, disclose or
distribute the information contained in this e-mail and any attached files,
with the permission of the sender.

This message has been scanned for viruses.
____________________________________________________________________________
___________

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

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

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




More information about the AccessD mailing list