Charlotte Foust
cfoust at infostatsystems.com
Tue Apr 4 12:46:57 CDT 2006
How can you move to EOF in an empty recordset? If you do a move on an empty recordset, it errors! Anyhow, I don't have Access 2003 installed, but of course Jet is there for the other 2003 apps that use it, so I suppose it's still a possible culprit. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Nicholson, Karen Sent: Tuesday, April 04, 2006 10:35 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Code stops working There is something about the .eof and .bof not working in Access 2003. You have to first move to .eof before you can find .bof. I know it is a bug, I don't know if they have fixed it yet. Karen S. Long Programmer Analyst EG&G Technical Services, Inc. Pittsburgh, PA Phone: 412-386-6649 Email: cyx5 at cdc.gov -----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 -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com