Resolving locking issues in vfp6.0

[RichardHall]

I have developed a multi user point of sale accounting application using visual foxpro 6.0.

I frequently encounter error 108 and 109 while updating the database. I've tried changing the "SET REPROCESS" a couple of times with little success. Forms use private data sessions and call the follow "SET" function in the initial event method.

&&&&&&&&&&&&&&&&&&&&&&&&&&&&
function SetsForPos()
set talk off
set compatible off
set deleted on
SET NEAR ON
set exclusive off
set safety off
set memowidth to 200
set status bar on
set clock status
set reprocess to 10
return
&&&&&&&&&&&&&&&&&&&

I'm looking for an experienced foxpro consultant to work with me to assist in resolving these issues.

Thx
Richard Hall
Rainier Computer Systems
(253) 840-5441
Rich@RainierComputers.com

 

[ramani]

Hi

These are 'file in use' and 'record in use' errors.
Obviously, either error trap has not been set correctly.

From the records are locked to the time records are released, do not allow the user interaction.

SET MULTILOCKS ON
SET REPROCESS TO 0

Use always TRANSACTION PROCESSION so that you can conveniently ROLLBACK if there is a need.

Use optimistic buffers unless it is a must that you have to use pessimistic buffers under the specific situation.

These are the general guidelines. More specific can be provided, if you present specific problem with code.




ramani
(Subramanian.G)

http://winnersoft.coolfreepages.com/

 

[ramani]

Hi

In an ideal situation, I use the code.

SET REPROCESS TO AUTOMATIC

However, in your situation, first set it to

SET REPROCESS TO 0
and after making sure that you never get a file locking problem, change it to AUTOMATIC.

The difference is that if 0, you can cancel by ESC and get back. If automatic, the system will freeze, if you have not set the way out.





ramani
(Subramanian.G)

http://winnersoft.coolfreepages.com/