[AccessD] Stored Procedure not producing results

>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()). 

Amen!  I do that regularly now.  It juts makes managing data so much easier
when you can see when it was entered.  I actually use the date + time so
that I can see things like how long an append query takes to run (time of
last entry in the "batch minus time of first entry in the "batch").


John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of artful at rogers.com
Sent: Wednesday, November 22, 2006 6:08 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Stored Procedure not producing results

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