T
Tim
Hello,
Is there a limit in Access 2000 of the amount of queries
you can link on top of each other? I have a query, which is
based on another query, which is based off of a moderately
large SQL Server table. This query has some sub-queries as
fields. These are querying different linked tables to find
specific data. The query runs fine by itself. However, if I
try to include this query in another query or as the source
for a form, nothing will happen when I try to run the form
or the top level query. Then when I try to close the window
I get a message saying that this will reset my code, do I
want to continue? If I click Yes, the message just pops up
again, and I can never get rid of it. I have to force quit
the DB, which then corrupts the db. I have checked the code
and am sure I have no infinite loops occuring. I am going
to try making my problem query into a make-table query, but
are there any other suggestions? Have you seen this before,
or know what causes it? And if so, is this no longer a
problem in Access XP or 2003? Thanks, any help is very much
appreciated.
Tim
Is there a limit in Access 2000 of the amount of queries
you can link on top of each other? I have a query, which is
based on another query, which is based off of a moderately
large SQL Server table. This query has some sub-queries as
fields. These are querying different linked tables to find
specific data. The query runs fine by itself. However, if I
try to include this query in another query or as the source
for a form, nothing will happen when I try to run the form
or the top level query. Then when I try to close the window
I get a message saying that this will reset my code, do I
want to continue? If I click Yes, the message just pops up
again, and I can never get rid of it. I have to force quit
the DB, which then corrupts the db. I have checked the code
and am sure I have no infinite loops occuring. I am going
to try making my problem query into a make-table query, but
are there any other suggestions? Have you seen this before,
or know what causes it? And if so, is this no longer a
problem in Access XP or 2003? Thanks, any help is very much
appreciated.
Tim