Union query works on two machines but not on a third

[Ray]

I have a union query that wrks perfectly on two machines but on a third it
gives message that says it is either incorrectly typed or is too
complicated. My question is how can that be given it works on other
machines?

One machine is set up in a similar way to the one that fails. The First is
a notebook with 1GB. Initially I wondered about the memory but that would
not seem to be relevant given that the other machine that work has the same
memory (512MB).

The biggest part of the problem is that the machine it is to run on is the
one on which it doesn't work.

If you have any thoughts at all I would be glad to hear them.

Ray Brown

 

[Van T. Dinh]

* The copy of the database may be corrupted. Try a fresh copy of the
database from the working PCs on the problem PC.

* Windows and Access use a lot of files and the machines may have different
file versions, especially that there are so many Updates / Service Releases
/ Service Patches.

Suggest you apply all available Updates / SRs / SPs for bothe Windows and
Office/Access on the problem machine and try again.

 

[Ray]

Thanks Van

I have already done updates to the problem machine and so far as I am aware
they should be at the same level of updates. I will however double check.

I checked the problem version on my home machine and it works fine.

The other thought I had was that perhaps Access itself was corrupt. I am
ready to reinstall Access just to be sure.

Any other thoughts would still be welcome so that when I get to the problem
machine again I can have the maximum chance of nailing the problem

Again many thanks for responding to my question

Ray Brown

 

[John Spencer (MVP)]

To do its job, Access (like most modern programs) makes use of various external
program and object libraries that provide functionality that may be shared among
applications. For example, Access always uses the Visual Basic for Applications
library, the version-appropriate Access Object Library, and the OLE Automation
library. References to the specific library files, including their locations,
are stored with your database. But these library modules may not be in the same
location on different machines, especially if they have different versions of
Microsoft Office. If you move a database from one machine to another, these
references may be "broken"; that is, one or more of the library files may not
be where the stored reference says it is.

When this happens, you need to take steps to let Access repair the broken
reference(s) ON THE COMPUTER WHERE THE FAILURE IS OCCURING.

Here are MVP Doug Steele's instructions for how to do it:

*** Quote ***

Any time functions that previously worked suddenly don't, the first thing to
suspect is a references problem.

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and where
it's being run (or the file missing completely from the target machine). Such
differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug window
on top" option). Select Tools | References from the menu bar. Examine all of the
selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you just
unselected (you can tell by doing a Compile All Modules), go back in and
reselect them.

If none have "MISSING:", select an additional reference at random, back out of
the dialog, then go back in and unselect the reference you just added. If that
doesn't solve the problem, try to unselect as many of the selected references as
you can (Access may not let you unselect them all), back out of the dialog, then
go back in and reselect the references you just unselected. (NOTE: write down
what the references are before you delete them, because they'll be in a
different order when you go back in)

For far more than you could ever want to know about this problem, check out
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

Just so you know: the problem will occur even if the library that contains the
specific function that's failing doesn't have a problem.

**** End Quote ****

So, follow those instructions and see if your problem goes away.

Check out the following reference
http://www.trigeminal.com/usenet/usenet026.asp?1036