G
Guest
This program was written by other people.
there are fifty buttons. One button one import.
program logic works like this.
1) press button "CIO"
2) copyobject "","CIO", actable, "CIO EMPTY"
3) do something. RUN queries. ("CIOSUMMARY")
4) When done deleteobject actable, "CIO"
This is the logic uesed on most of the buttons. Keep in mind the copyobject
and deleteobject. I believe they are the keys to my problem.
They problem is this. The Join's in the CIOSUMMARY query are removed. ????
It looks like to me that something in Access is causing Access to
re-evaluate the queries. If the query is found to be broken then it is
"Fixed"???
Example: CIOSUMMARY has two tables(CIO and Maginfo) they are joined by the
MCODE. Since the table CIO does not exist and "joins" cann't link nothing to
a table then the "join" gets deleted and because of that some fields get
renamed.
Results, the query works differently if at all.
The Questions:
What causes Access to re-evaluate queries?
Can I stop it?
Am I missing something here?
Scott Burke
there are fifty buttons. One button one import.
program logic works like this.
1) press button "CIO"
2) copyobject "","CIO", actable, "CIO EMPTY"
3) do something. RUN queries. ("CIOSUMMARY")
4) When done deleteobject actable, "CIO"
This is the logic uesed on most of the buttons. Keep in mind the copyobject
and deleteobject. I believe they are the keys to my problem.
They problem is this. The Join's in the CIOSUMMARY query are removed. ????
It looks like to me that something in Access is causing Access to
re-evaluate the queries. If the query is found to be broken then it is
"Fixed"???
Example: CIOSUMMARY has two tables(CIO and Maginfo) they are joined by the
MCODE. Since the table CIO does not exist and "joins" cann't link nothing to
a table then the "join" gets deleted and because of that some fields get
renamed.
Results, the query works differently if at all.
The Questions:
What causes Access to re-evaluate queries?
Can I stop it?
Am I missing something here?
Scott Burke