Charlotte Foust
charlotte.foust at gmail.com
Fri May 25 09:31:06 CDT 2012
Access problems are harder to track down than dot net problems, especially in reports. Looking at the data lets you know whether what you thought was working is actually doing what you intended. Glad you got it resolved. Charlotte Foust On Thu, May 24, 2012 at 9:49 AM, Brad Marks <BradM at blackforestltd.com>wrote: > Charlotte, > > I am all smiles. > > The cause of the problem was not an Access bug, but rather a dumb mistake > on my part. > > Because the error was only surfacing once in a while it was difficult to > track down. > > In order to see that actual data that was being fed to the report, I added > code to push the data to an Excel file when the report was being opened. > (Remember, this report is run automatically each night). To my surprise, > I found that each automated run was creating two Excel files. > Hmmmmmmmmmmmmm this didn't sound right. > > I then discovered that the report was being opened an extra time > (left-over test code). > > Apparently, this extra open did not cause a problem some nights and it did > cause a problem on other nights. I am guessing that this is based on how > busy the system was when the report was generated. If the system was slow, > the extra report open does not seem to cause a problem. If the system is > fast, the extra report open causes a problem. > > Anyway, your suggestion to look at the data, prompted me to export to > Excel, which lead me to discover the extra Excel files, which lead me to > find the extra report open. Therefore, you get the credit for this one! > > Thanks, > Brad > > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com on behalf of Charlotte Foust > Sent: Wed 5/23/2012 9:30 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Intermittent Errors on Access Report > > I've seen EVERYTHING occur in an Access report! LOL > > If you can't find a way to trigger it intentionally, it's pretty hard to > troubleshoot. I'd start by looking at the data to see what's different > about the record that breaks and the ones that work. It sounds like you > might have run past the end of a dataset but that's just guessing, If > you've got grouping and sorting going on dig into that. > > Charlotte Foust > > On Wed, May 23, 2012 at 8:28 AM, Brad Marks <BradM at blackforestltd.com > >wrote: > > > All, > > > > I recently ran into a very strange intermittent error that has me > puzzled. > > > > We have a small (2 page) Access 2007 report that is automatically > > generated every night. > > > > Most of the time, the report is generated perfectly. However, > > occasionally errors are generated. > > > > When this occurs, it always happens when the first detail line of page 2 > > is being generated. > > > > Page 1 is generated perfectly (Page header, detail lines, page footer). > > On page 2, the Page Header, Page Footer, and Report Footer are all > correct. > > > > However, all four fields in the first detail line show "#Error" and none > > of the remaining detail lines are shown for page 2. > > > > I have dug into the report and cannot see anything strange. Because this > > problem only occurs intermittently, I am not sure how to track it down. > > > > Has anyone else ever seen something like this occur on an Access report? > > > > Thanks, > > Brad > > > > > > -- > > 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 > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > > > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > >