[AccessD] Code stops working

Well, that's another thing I've noticed since I installed 2003/VS 2005:
the code compiles but it still may break at runtime!  However, to answer
your question, it all compiles, there are no broken references, and all
the usual suspects have been hauled in for questioning.  It's one of the
more maddening things I've run into in a history of being driven crazy
by Access. :-< 


Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim DeMarco
Sent: Tuesday, April 04, 2006 10:33 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Code stops working

Charlotte,

The one thing I've noticed when code stops working is that there may be
some bad code elsewhere.  Have you tried compiling your code and seeing
if the compiler can find anything untoward?


Jim DeMarco

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
Sent: Tuesday, April 04, 2006 1:10 PM
To: AccessD at databaseadvisors.com
Subject: [AccessD] Code stops working

Has anyone else seen this?  We have code that has worked for 3 years and
suddenly, it fails.  The code can be very simple like "If Not (rst.EOF
and rst.BOF) Then"  and even though both EOF and BOF evaluate to true,
the next line of code will execute!  I've seen this in several places.
And we have signature handling in one of our apps.  The subforms, which
all have the same kind of code, raise a custom event which is sunk by
the parent.  On some subforms, the event may raise the first time but
not after that.  Making a change in the code in either the child or
parent might make it work ... Once.  Then it returns to ignoring the
raise event line.  It steps through it, but the event is never sunk in
the parent form.  The exact same code works in other subforms.  I've
tried compact and repair, decompile, creating a new form and copying the
controls over, then exporting the code from the odd subform to text and
pasting it into the module for the new form.  Same behavior.  These are
very complex subforms and the parent form is worse.  

I just recently upgraded to Office 2003 on my machine (we're still using
Access 2002) and I'm wondering if that has caused the strange behavior.
The others in my office have had 2003 for a while, but I dragged my
heels on it.  We're also working in VS 2005 and have the latest source
safe version, so it may be an ugly combination of things, but has anyone
else had a similar experience?  Code that worked on Friday was broken on
Monday!  Yikes!

Charlotte Foust
Infostat Systems, Inc.
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


 



************************************************************************
***********
"This electronic message is intended to be for the use only of the named
recipient, and may contain information from Hudson Health Plan (HHP)
that is confidential or privileged.  If you are not the intended
recipient, you are hereby notified that any disclosure, copying,
distribution or use of the contents of this message is strictly
prohibited.  If you have received this message in error or are not the
named recipient, please notify us immediately, either by contacting the
sender at the electronic mail address noted above or calling HHP at
(914) 631-1611. If you are not the intended recipient, please do not
forward this email to anyone, and delete and destroy all copies of this
message.  Thank You".
************************************************************************
***********

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