There is the possibility that the failure is in [Query4 5B All Union] or in the
queries it is using to do the union. The thing I usually suspect when something
works on one computer and fails on another is the library references.
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
thank you for your idea,I've tried it but unfortunately no luck, I really
dont understand why it happen on certain computer only,please somebody I want
some explaination
John Spencer (MVP) said:
I don't see any reason this would fail from what you have posted. I would try
surrounding section with brackets since that is a reserved word for Access.
That really doesn't explain why it acts up on some computers and not others.
Beyond that GUESS, I don't see what could be causing the problem.
TRANSFORM Sum([KM]/1000) AS KM1
SELECT [Query4 5B All Union].CusItem1
FROM [Query4 5B All Union]
GROUP BY [Query4 5B All Union].CusItem1
PIVOT [Query4 5B All Union].[Section]
Greeting to all expert out there,
Im a little puzzled right now,
I tried to run this querry:
TRANSFORM Sum([KM]/1000) AS KM1
SELECT [Query4 5B All Union].CusItem1
FROM [Query4 5B All Union]
GROUP BY [Query4 5B All Union].CusItem1
PIVOT [Query4 5B All Union].Section;
and this message : "Join expression not supported" came out.
Fyi, when I try to run this querry on other machine it will run without any
problem. Im using a Dell notebook and some of my friends using Fujitsu
notebook encountered the same problem
Please help me.Im using Microsoft Access 2000 Professional Edition
(9.0.2720)on Windows 98 platform.
thank you
