David Emerson
newsgrps at dalyn.co.nz
Wed Nov 22 11:56:55 CST 2006
I tried: 1) Running the query using dates from 2 months ago 2) Deleting all the data so that it was back to where it was two months ago and running the query using dates from 2 months ago. Neither test worked. Maybe it is a structure change. I will try comparing tables to see if there is any differences. David At 23/11/2006, you wrote: >If the structures haven't changed, then the data is the villain. But >you have a concrete clue to work from. Devise some scope that will >include only the data from two months ago and verify your assertion. >Then expand the scope to "two months ago plus a day" and run it >again. Repeat until failure. > >This assumes of course that the scope is expandable so easily. (A >good reason to have a "DateEntered" column in every table, which >defaults to GetDate()). > >----- Original Message ---- >From: David Emerson <newsgrps at dalyn.co.nz> >To: Access Developers discussion and problem solving ><accessd at databaseadvisors.com>; Access Developers discussion and >problem solving <accessd at databaseadvisors.com> >Sent: Tuesday, November 21, 2006 10:53:58 PM >Subject: Re: [AccessD] Stored Procedure not producing results > >Worse - my database from two months ago works fine, but the latest >version is the one that is causing the problem. This may indicate a >data problem perhaps? > >David > > > > >-- >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com