It is certainly possible you're dealing with a damaged database, or perhaps
even damaged indexes.
Furthermore, moving a table little bit could force the query processor to
build a new query plan, because perhaps it thinks that you've modified the
query again. Forcing the database engine to *re* build a new query plan
could perhaps cause it to see some new records.
On the other hand, perhaps there some default like now() that has a time
based criteria that actually changed or rolled over during the time when
you
changed the table, and it simply occurred at the same time. (for example
of
this occurred at twelve midnight, you could have new date criteria now
show
up).
On the other hand, if you're saying this is a completely repeatable
occurrence that you can do over and over, then something else strange is
indeed going on here.
So, if this was just a one time occurrence, then I not much surprised at
all, since changing things in a query in design mode causes the query
processor to rebuild and recompile the query plan and even the statistics
that JET will use for the query.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@[EMAIL PROTECTED]
|
