Could not save: currently locked by user admin . . .

We have been struggling with a problem for several months involving our Access Control Card software (Number Five Software, Card five Professional v8.7).

The software uses any standard web camera to capture the image of an associate and print/save. The software uses a Microsoft Access2003 SP3 database.

When I take a photo:
1.      I get an error message.
2.      The card will print after the error message is displayed twice.
3.      The photo is NOT saved to the MS Access db.

The error message:
Cardfive Vision 8.7 Professional
N5 Database Kernal
Database Error - SAL Statement execution
error SQL State = HY000 SQL Driver
Code=-1105  [Microsoft][ODBC Microsoft Access
Driver] Could not save: currently locked by user
'admin' on machine 'VSAT4W61JH1'.
(Dbconn.cpp:2773)[Microsoft] ODBC Microsoft

                                [Help]  [Close]

We have done the following:
1.      Worked with the software vendor for several months ā€“ no solution.
2.      Eliminated the original Logitech software,
3.      Used a generic driver,
4.      Replaced the Logitech camera with a Microsoft camera.

But, we still get the same error.

What am I missing? What can I try?

NFiveError.bmp
Tom WinslowAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
INHOUSERESConnect With a Mentor Commented:
Final word...
Go back to how it was and slowly change things one by one.
One of the variables you changed isn't working.
0
 
INHOUSERESCommented:
what machine is "VSAT4W61JH1"?
0
 
Tom WinslowAuthor Commented:
That is my company supplied DELL laptop. The software and drivers are also on the DELL Laptop.
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
INHOUSERESCommented:
so this computer is the compuer that's getting the error.
In otherwords, it's locked itself out of the database?
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<1.      Worked with the software vendor for several months ā€“ no solution.>>
  The problem is, it's a bug in their code of some type or someone else is really in the file and preventing you from doing something.  But really that comes down to a matter of design of the app.
JimD.
0
 
INHOUSERESCommented:
Not necessarily, because the code is simply trying to run a query.
It could be that the database is having issues processing the requests, not the app that's requests them.

Tom, Has this occured after an update by the original company?
If so, then it is their fault and you should be asking for their help (or asking for your money back!)

Is the software open source? Can you see the VBA? I highly doubt you can, but if you can, show us the code.
0
 
Tom WinslowAuthor Commented:
Tom, Has this occured after an update by the original company?

<<<  Yes, The problem came abut once w did a major update, on a new laptop, with a new card printer. Too many variables changed at one time.  >>>

If so, then it is their fault and you should be asking for their help (or asking for your money back!)

Is the software open source? Can you see the VBA? I highly doubt you can, but if you can, show us the code.

<<<  No, the software is not open source.  >>>

tw

0
 
INHOUSERESCommented:
Tom, it may be long winded, but if a lot of variables have changed you might have to go back and step through them with tests to see what is causing the problem.

This isn't just for our benefit, because even the company that supply this to you can't really do anything until you can get this piece of information.

My initial thought is that it's the laptop which is the problem.
There has to be a setting or a user restriction on the SQL software which is causing the error.

HOWEVER... a microsoft update screwed my system the other day with DAO recordsets.
I doubt it'll help but it can't do any harm at all:

Click Start > Run
Type CMD then press enter.
Copy this:
Regsvr32.exe "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.DLL"
in command prompt, right click and click paste then press enter.

As I said, it can't hurt.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<1.      Worked with the software vendor for several months ā€“ no solution.>>
I really am curious; what was their take on the situation?  
Really it sounds like an app design problem.  
JimD.
0
 
INHOUSERESCommented:
Just read this on thier site, I assume you've seen it?

Concerning the ODBC error that sometimes occur, please update your MDAC to the version 2.8 available in http://msdn.microsoft.com/data/.
If the error still occurs please contact the NFive Tech Support with more information about it. Also make sure that the database is not being accessed by more than one process at the same time for writing purposes. If the process is running in a slow machine, the windows locking methods may fail and the N5 Database Interface may issue the SQL Statment Execution Error message. This exception has been noticed under rare circumstances when using more than one Auto Print session involving the same database resources.

See this link and tut on how to find your current version:
http://support.microsoft.com/kb/301202

I doubt this would be an issue if it's a new laptop.
0
 
INHOUSERESCommented:
I've just noticed the error message is incomplete.
Not sure how you could provide the rest of it, but if you can, it may help.
0
 
Tom WinslowAuthor Commented:
The software vendor has provided an update. I am hoping that this will resolve all of the issues.
0
All Courses

From novice to tech pro — start learning today.