Error 3197 for just one user

[kagard]

Greetings:

I made some changes to our company's database front end and installed
the revised front end on several machines. Most users can create sign
in sheets. One use cannot, and Access displays Error 3197 when she
tries. I've closed the db on all other machines, but she still gets
the error. Its the same db on all machines, and the code that is
failing is unmodified. I looked (without success) for a stray ldb on
her machine or on the server that hosts the back end mdb.

Any idea what would cause this one machine to fail on unmodified code
that was working before the upgrade? TIA...

Keith

 

[Danny J. Lesandrini]

what is error 3197?

 

[Keith]

Hi:

3197 basically says that two users are trying to update the same data
at the same time.

I reinstalled the db from the same original on my flash drive and it
works.

K

 

[Gina Whipp]

Keith,

If this error is *...you and another user are tyring to make changes..."
then... Did you try giving the User a new front end? I would also check
the Users permissions to be sure they match with everyone elses.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[John Spencer MVP]

Usually, when I see this type of problem I expect to see a references problem
on the problem machine.

When this happens, you need to take steps to let Access repair the
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://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-2009
The Hilltop Institute
University of Maryland Baltimore County

 

[a a r o n _ k e m p f]

SEE?

Jet isn't reliable enough for a _SINGLE_FUCKING_USER_

upsize to SQL Server and don't listen to these jet retards
SQL Server is free and it has been for a decade.

there is no point to using Jet for everything-- all it does is
crash..
and SQL Server development is _EASIER_ because you can use
professional-level tools like SQL Server Management Studio

-Aaron