Sending objects in a database for purpsoe of updating another database

[Abacus1234]

If I package a number of objects in a database, with the intention of sending them to another site to be used to update a remote data base. Some queries default to expr. In these cases we also package the tables in the database, and the queries remain true. It would be of interest to know why this happens in some cases but not in others. And is there anyway to stop it happening? Thanks for any insight.

[pbaldy]

I wouldn't expect a query to do that unless it's opened in design view and the table isn't there. Are you saying it does? If so, one potential culprit is Name Autocorrect, which has been called Name Autocorrupt. Try turning it off if it's on.

[Abacus1234]

Thanks, I will definitely check that out.

[pbaldy]

No problem. Post back with results; I'm curious what can cause this other than opening the query.

[Abacus1234]

We were wondering if you thought that doing a Repair and Compact on what we call the "Feeder Database" could also cause anything like that to happen.

[pbaldy]

That's possible. Looking at:

http://rogersaccessblog.blogspot.com...my-access.html

I note:

Thirdly, it rebuilds the table statistics which are used by the query optimizer to optimize queries. It also forces a re-compile of your saved and embedded queries based on these new stastics.

It could be that the re-compile sees that the table doesn't exist and "fixes" the query for you.

[Abacus1234]

Thanks, that's really helpful. Will do some testing and tell you if we find that the Repair and Compact or the Auto Correct are "fixing some queries for us".

[pbaldy]

If so, it's a "feature", not a "bug".

[Abacus1234]

I did some limited testing.

I took 2 queries, one of which had ended up with expr in each field, and one that had remained unaffected.

I pulled them into a "feeder database", did NOT repair and compact, then used them to update another database, they both remained unaffected without expr finding it way in.

I pulled them into another "feeder database, which I did REPAIR and COMPACT, then used them to update another database, One was affected and one was not.

The one that was affected and ended up with expr in all columns, looked only at one table.
The one that was NOT affected, looked at the same table plus 2 other tables.

So it seems that Access slightly over-reached to be helpful with Repair and Compact... thanks for the lead to this aspect of the problem, now we know what not to do.........

I'm flying south for a few days, so the testing will be halted until I return.

[pbaldy]

No problem, though you're the one that asked about it, so you get the credit.