Working on 1 pc, but not an other one

[dixxy12]

Hi,

I have a reoport that qets populated based on a Union query. The problem that i am having is that same report does not work on all computers. It work on mine (Win XP, Access 2002), but won't work on an other system same Os same version Access.

It will work on a Windows 2000 Pc, with Access 2002, but not on an other 2k box with the same version of Access.

Has anybody had something like this ever happened to them?

Where should i look to try and find the problem?

I'm at a lost here on this one...

 

[randy700]

Check for missing references.

Randy

 

[lameid]

I hate to ask this but are you sure they are running against the same data? (Maybe drive X: is different on each machine ; they are linked to different copies of the data; or there are no links and the copies are different).

Are both installs of Access and Windows fully patched?

If you run the select statements individually do they give the same results between systems?

Is there some criteria that is somehow user dependant? I.e. use of currentUser() or Environ("User")

 

[dixxy12]

Thanks Guys for the hints...let me look at these possibilyties and report back....

 

[missinglinq]

I suspect Randy's suggestion should be the first thing to do! Anytime apps run fine on one machine and not on others the first thing you have to think about are missing references. If you've never had occasion to do this, here are Doug Steele's instructions on how to troubleshoot the problem:

*** 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://www.accessmvp.com/djsteele/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 ****


The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!

 

[irishjoe]

Just had a thought, does each user on their computer have the same level of access? Like user or Admin... Or if its the same user on different computers, do you have the same rights on each one?

 

[PHV]

Anyway, please define: does not work

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886