The Reps team have been experiencing that Access 2002 unexpectedly
quits
while working and also lots of Corruption Failures and "Record lock
can not
update" messages since the upgrade from Windows 2000 and Access 200 to
Windows XP and Access 2002 (XP) was done.
Now, they are working and at anytime in anywhere of the application
access
unexpectedly quits with no error messages and the info that was being
entered
is lost.
all computers have a standard configuration with the latest services
packs,
Microsoft Windows XP SP2 and Microsoft Office 2002 (XP) SP3, Microsft
Jet
4.0.8618.0, y have also check all the references and they are good.
Here are the references:
-Visual Basic for applications
-Microsoft Access 10.0 Object Library
-Microsoft Office 10.0 Object Library
-Microsoft Office XP Web Components
-Micrfosoft ActiveX Data Objects 2.8 Library
-OLE Automation
I heard something about Opportunistic locking if you disable it
(Oplocks) on
the server may reduce the risk of data corruption.
This problems occurred in an .mde file, but i also have experienced the
same
problem and i am working with the .mdb file
I've been dealing with this problem since 7/12/06 (more than 2 weeks)
doing
lots of different things like changing references, disabling and
enabling the
"open databases using record locking", compact and repair, migrate
database
to access 2002, contacting Microsoft co (The suggestions they gave did
not work)., etc.
Sometimes I have the opportunity to debug and the error usually comes
in
the next part (testing with a total of 3 users saving a new contact
record each user and saving all simultaneously at once), after the
other users are done saving when i got the error message then click on
cotinue process and it saves with no problem.
Code:
Sub WriteAuditlog(txtOperation, txtTableName, txtFieldName, frefnum,
OrgValue, CurValue)
Dim rstAudit As ADODB.Recordset
Dim fsql As String
On Error GoTo Err_WriteAuditlog
Set rstAudit = New ADODB.Recordset
Set rstAudit.ActiveConnection = CurrentProject.Connection
rstAudit.CursorType = adOpenKeyset
rstAudit.LockType = adLockPessimistic
fsql = "Select * from AuditTable"
rstAudit.Open fsql ======================IT WILL BREAK HERE
rstAudit.AddNew
When i continue the execution after the message catastrophic failure it
saves the contact record with no problem.
Does anybody know what could be happening? if you need any more
information please let me know. Thanks for your replies, any help is
appreciated!