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

Oh I wish I had that option as that is what I used to do in my other
position.  In my new role it is only Office 2007 and nothing else (with the
option of going to A2010).  Depressing but true.

A2007 really was not ready for release. It is full of weirdness and strange
behaviour.  I am not talking about having to do thing differently because
they have changed (such as the ribbon). I mean genuine oddness where things
don't work, changes aren't always saved,  Events are allowable, but won't
trigger.  Wow - the list goes on.  Maybe it is good if you are using as a
glorified spreadsheet, but for development work is has been far from stellar
in ease of use.

Ok.. whine mode off. :)

Thanks for all your advice



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

I still  develop in 2003.  I then open the resultant MDB in 2007 and save it
as an accdb.

I find I'm far more productive that way.


-- 
Stuart

On 9 Aug 2011 at 20:02, Darryl Collins wrote:

> 
> ______________________________________________________________________
> _________________
> 
> 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