Re: Queries and Now()
- From: "Amy Blankenship" <Amy_nospam@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 6 Feb 2008 16:05:38 -0600
"Craig" <msaccess@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:uA3jNaQaIHA.5768@xxxxxxxxxxxxxxxxxxxxxxx
Could you say that again in English? ;-)
"Michel Walsh" <vanderghast@VirusAreFunnierThanSpam> wrote in message
news:ug32N0NaIHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
I suspect your ASP implementation optimizes something it should not. It
may also be version dependant, such as ASP.Net 3.5 or previous versions.
Sure, that sounds like I try to send the problem to ASP, but if the query
behaves correctly within Access... Can you try to get the data from, say,
Excel, or from MS SQL Server, or from a dataview tool from C#, to see if
it get as Access, or as your ASP implementation shows it, letting Excel
(MS SLQ Server, C#) determines who is the source of the problem, kind of
... :-)
I think what he is saying is that the problem is probably in your ASP code
and not the query. So probably in the loop where you think you've changed
what you're looking at, you're changing it for everything but the
misbehaving field. So maybe you store that field's value above the loop,
and you're always retrieving the same value.
.
- Follow-Ups:
- Re: Queries and Now()
- From: Michel Walsh
- Re: Queries and Now()
- References:
- Queries and Now()
- From: Craig
- Re: Queries and Now()
- From: Michel Walsh
- Re: Queries and Now()
- From: Craig
- Queries and Now()
- Prev by Date: Re: Queries and Now()
- Next by Date: Re: Multiplying field in query
- Previous by thread: Re: Queries and Now()
- Next by thread: Re: Queries and Now()
- Index(es):
Relevant Pages
|