| edlyons@mail.com 2005-09-28, 11:24 am |
| I have a VB6 application that is getting intermittent 3260 errors. The
database is on a Win2000 network server. The database has a "job"
table that points to other databases. In order to "lock" the job a
field is set to true in the record when the user wants to perform an
action on the job. I have a dummy table in the database which I open
with dbDenyWrite before I open the job table to make sure this user is
the only one who makes the notation in the job record ("unlock" works
the same way except the field is set to false):
Open dummy with dbDenyWrite
Open tblJob with Select * From tblJob Where ID = 1
Edit the record
Update the record
Close tbjJob
Close dummy
This has been working for many years in hundreds of installations
without failure.
In the last year or so one of the installations is reporting an
intermittant 3260 error. Typically, it's ComputerB locking out
ComputerA, but sometimes it's the same computer (just a different
application using the same database). This installation has about 10
users on a Win2000 network. All client computers are running DAO
3.60.8618.0 and Jet 4.0.8618.0 with at least 512MB of RAM.
The application has the facility to do logging so I had them turn it
on. Basically, every operation is logged from the time the program
starts until it is terminated. The log shows many job "locks"
successfully executed as noted above. When the job is "unlocked" it
works the same as locking except the notation in the record is removed.
The application "thinks" that the recordset was closed.
Another user comes along (could be a different computer or the same)
and opens another of my applications that uses the same database (and
facilities) and if they may get the 3260 error on a tblJob record that
was "locked" and "unlocked" hours before (verified through the logs).
The network administrator at this site believes it is my application
software and I believe different (because the logs show open and close
operations completed sucessfully and this is the only installation that
gets this error).
I don't know the correct questions to ask about the network setup, etc.
I have looked through the volumes of newsgroup entries for days looking
for an answer but nothing. Any help would be greatly appreciated.
Ed
|