Query Reverts To Previously Saved Version

  • Thread starter Thread starter Smartin
  • Start date Start date
S

Smartin

Hello All,

Using Access 97. This is just a curiosity I am wondering if anyone else
has experienced.

I have a query like

01) SELECT Soups, Nuts FROM MyTable WHERE Soups IN (
02) 'paste', 'your', 'soups', 'here'
03) );

FWIW MyTable is a linked table in another A97 database.

I reuse this query daily by pasting new values in the IN list on line 02
and immediately running it.

Occasionally the results match {'paste', 'your', 'soups', 'here'} (i.e.,
the saved version of the query) rather than the new values I pasted only
moments before. When I switch to the SQL view, sure enough, my newly
pasted values are gone and the query has reverted to the saved version.
This happens sporadically, sometimes daily, other times maybe once a week.

Has anyone seen this behavior?

The work-around, which is simple enough, is to save the query with the
new values before running it. The only objection to doing this is it
strips the "instructions" for other users.
 
a lot of times

no help

Pieter

ps
usually making sure all objects are "killed" (ie set obj =nothing) +
repair, compact & decompile tends to ward it of - most times <g>


Smartin said:
Hello All,

Using Access 97. This is just a curiosity I am wondering if anyone else
has experienced.

I have a query like

01) SELECT Soups, Nuts FROM MyTable WHERE Soups IN (
02) 'paste', 'your', 'soups', 'here'
03) );

FWIW MyTable is a linked table in another A97 database.

I reuse this query daily by pasting new values in the IN list on line 02
and immediately running it.

Occasionally the results match {'paste', 'your', 'soups', 'here'} (i.e.,
the saved version of the query) rather than the new values I pasted only
moments before. When I switch to the SQL view, sure enough, my newly
pasted values are gone and the query has reverted to the saved version.
This happens sporadically, sometimes daily, other times maybe once a week.

Has anyone seen this behavior?

The work-around, which is simple enough, is to save the query with the new
values before running it. The only objection to doing this is it strips
the "instructions" for other users.



--
 
Pieter said:
a lot of times

no help

Pieter

ps
usually making sure all objects are "killed" (ie set obj =nothing) +
repair, compact & decompile tends to ward it of - most times <g>


news:[email protected]...

Interesting. Do you get this with linked tables, local tables, both?

My setup is nothing fancy. One linked table, one query.

Thanks for the feedback.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top