strange problem

[JString]

One of the users of my database is having a strange problem that seems to be
local to her machine. For some reason, a portion of the database doesn't
function at all for her, but the rest of it works fine.

Here are some possibilities that I've eliminated so far:

It's definately local to her machine only. I had her try her account on
another machine, which worked fine, and I had someone else try his account on
her pc and he had the same error.

The front end app is fine. I deleted her old copy and reinstalled a fresh
copy and the same error occurs.

I checked macro settings and everything looks to be correct. Macro security
is set to low so that the front end's code should execute without any
problems.

Does anybody know of any possible causes to this problem?

 

[Beetle]

"a portion of the database doesn't function at all for her" doesn't give
us much to go on. Can you be more specific?

It would also help to know which version of Access is on the affected
computer.

 

[John Spencer]

Usually when something works on one computer and fails on another I
suspect a references issue.

To do its job, Access makes use of various external program and object
libraries. ON THE COMPUTER WHERE THE FAILURE IS OCCURING check (and fix)
the references

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://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 ****

'====================================================
John Spencer
Access MVP 2002-2005, 2007
Center for Health Program Development and Management
University of Maryland Baltimore County
'====================================================

 

[NetworkTrade]

I've seen one machine that would throw the "insufficient memory" error when
running some queries..... could only be cleared via rebooting....and I've
concluded it is something flaky on that machine - not Access.

On several machines that have a problem involving generating Reports - it is
documented that the printer driver is the cause...even in Preview mode.

You should double check your version and library references

hope this helps....

 

[Armen Stein]

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

That's true. Another thing to check is the Service Pack level on each
PC, as well as any other patches. For example, Access 2003 SP3 has a
recommended hotfix that should be applied.

http://support.microsoft.com/kb/945674

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

 

[JString]

Here's some more background info incase it helps.

There were no changes made to the database that would have caused this
problem. The user also has the same version of access 2003 windows 2000 that
everyone else does, and this hasn't changed either.

As far as I know, she was able to use the database without any problems
until a couple of days ago when our IT guy upgraded the server from NT to
Server 2003. I don't think he made any changes to her machine.

 

[NetworkTrade]

if not yet resolved; you can try a Repair feature available in Office (not
sure if Office2000 though...).... when you go to re-install Office into a PC
that already has Office it will offer you the choice to reinstall, cancel or
repair.... using the repair feature has fixed once an issue with Access that
was otherwise making no sense...

hope this helps