Why do 2 different Access processes lock each other

[pieeater]

I have a Windows 95 pc with 2 different access 97 database processes running. These processes are doing a similar job, they have forms sitting on a timer wait, and every 5 minutes they 'wake up' and check if there are any records in an AS400 file using ODBC. Any records found are read and used to update tables in an Access database on our Novell Ethernet network. Recently a problem has occured where the pc seems to freeze (the pc clock stops, but the mouse still works). If I do a Ctrl/Alt/Delete, windows tells me that one of the access programs is 'not responding'. If I end that task, the other access program jumps into life. This problem is occuring frequently, but randomly - I cannot recreate it on request. Has anyone any ideas where I should start looking ?

 

[Guest_imported]

I suggest you get on your knees and pray to the good lord

 

[jahlmer]

For starters, what you should look into is range-locking. Check the following URLs:

http://support.microsoft.com/support/kb/articles/Q131/0/50.asp

http://support.microsoft.com/support/kb/articles/Q87/8/82.ASP

Hope you can find this useful

Jahlmer

 

[mac318]

Pie-eater. Back in the 'good ole days' before networks became sophisticated, we used persistent flags (semaphors) to assure that a two processes did enter into a 'deadly embrace' which is what you are creating. In a table place, a field to hold a boolean flag. Before a process begins, it checks the flag. If the flag is set to true, it sets the flag to false and begins running. Upon completion, the process resets the flag to true. When the next process checks the flag, it won't run until the flag becomes true.

mac

 

[mac318]

correction to previous entry. Should read, "... did NOT enter into a 'deadly embrace'.

mac