Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Import queries prior to tables 1

Status
Not open for further replies.

jsteph

Technical User
Oct 24, 2002
2,562
US
Is there a setting where I can import queries without Access doing whatever checks it apparently does as it imports them?

What's happening is that I import these queries prior to the tables on which they're based--but I don't open them yet. The reasons for not yet importing the tables first are too much to get into.

The bottom line is that when I do import the tables, and then open the queries in design view, all the joins are missing. I'm assuming this is because Access tried to 'help' and parse the query, and couldn't make the joins because the tables didn't exist--so it made the unilateral dicesion to save the basic selects with all tables in the FROM clause--but no joins. In other words, it changed my code. Is this an option that can be turned off, or am I off-base in my assumptions about why this is happening? Thanks,
--Jim
 
Are you importing the queries with TransferDatabase?
 
No, I'm just using the menu item Get External Data/Import.
--Jim
 
In my version of Access (2000), I do not seem to have this problem with either method of importing queries. Just guessing, but have you turned off Name Autocorrect?
 
I'm in Access 2003. And yes, I think you've hit it. Tried to reproduce it and it did not work--but I had turned Name Autocorrect off before because of another major corruption that Name Autocorrect caused. So I turned it back on, then reproduced the problem and it happened as it did orignally.

I think Name Autocorrect is a massive scourge of Access. I suppose there may be some for whom it 'helps', but it's my guess that it hurts far more than it helps and the hurt it inflicts is far more devastating than what little help it may give. Ugghhh!!
Thanks for pointing me in the right direction on that,
--Jim
 
I think the responsible thing for Microsoft to do is in one of it's updates to turn off Name Autocorrect as the default.

Unfortunately they were not responsible enough not to keep this highly buggy feature out of the original release. Apparently having as many "features" as possible is more important than having a stable application.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top