I am writing an application to transfer data from an old database to a
new database.  While writing to the new database, I am getting the
message "Cannot save;  currently locked by user 'Admin' on machine
'BRIAN'."  The problem *does not* occur on the same table each time -
it varies, but has always been one of two tables, both late in the
procedure.

I have already whacked all the .ldb and .mda files I could find.  I am
running Win95, but I went into system.ini to disable vshare.exe to
make sure that was not the problem.  I also used autoexec.bat to load
share.exe, and increased the locks to 1,000.  This had no effect
whatsoever on the problem.

Any hints?

The 2.5 update may solve your problem.  It is available from FTP at Microsoft and on Technet.

/Peter

It seems to that you have two instances of your program, and both of
them attaches to the same database. If this is right, you do have to
handle multiuseraccess in your program code.

As you probably know, edit/addnew - update, seek, and most of the
other database operations lock pages or entire tables. The problem is
the unlocking. This happens in a background process. My experience is
that you have to tell the jet engine to do this background process.
The statement I use after all operations that locks parts of my
database is:
VB4: DBEngine.Idle dbFreeLocks
VB3: FreeLocks

Hope this helps!