Problem, getting waiting for lock in SO module, also when using Sys Manager to unlock a user too

[titoneon]

Hi Guys,
There is something strange happening in SBT 5.0 PRO, just recently, we never had this problem before but after we pack tables and closed the period at the end of the year, this is happening.

1- when a user gets Lock in SBT 5.0 PRO as you know, you can go to Sys.Manager then Transaction, System Recovery, Clear Flags and CLear all flags , then you input there the "Company number", "the Application ID" and "user ID", At least this is what we always do if someone got stuck in Sbt, It seem that it only happens when the user is using the SALES ORDER module, then we use the system manager to reset this user and then we go through the process of clearing that user but then, at some point the process of clearing Stop and a window pop up saying "Cancel or continue" and when we look at the left bottom we see there a message saying "waiting for lock ", so what we do is just select "continue" and the process keep going to the end and the user got cleared, this was not happening before and i don't know what is causing that or how to fix this.

2- second we got a few users using the SO module and for example today, only one user was using SO in company 04, so it was trying to save a sales order and he got a message "waiting for lock", it does not make any sense cause this is shared table, second it was not another user using "SO", in that company and even if it was any other user we did not have that problem before, i meant the "waiting for lock".

I am wondering if anyone have any suggestions on what can i do to fix this, i have the idea that maybe some system tables got corrupted but we have been indexing, and the problem happens at random.
Any help is very appreciated
Thanks
Ernesto

 

[titoneon]

Sorry, in the section that i said "Cancel or continue" instead is "Retry or Cancel", if we select cancel the program continue and clear the user, the table to be locked is Sotran04, where 04 is the company number.
Ernesto

 

[fitedgar]

My first suggestion is to get everybody out of SBT.
After, go into the server and close all files in the SBT folder. or Re-start the server.
Re-index all files.
I have seen this problem where the user is cleared in SBT, but the network still has the file opened.

Edgar
Integrated Bar Code Systems, Inc

 

[titoneon]

Hi Edgar,
Thanks for the suggestions, and that is true, even when we cleared the user from SBT still in the server from server manager i can i see users still current using the sbt dbf and cdx files.
I found what it was, it was an appl. that i did in vfp 5.0 that use sotran.dbf, but the use of that dbf was shared, i can see, that can affect the file reindex, but should not affect a user to save a so or system manager to clear a user, so what i did was, i change the code in the appl. by using the dbf as "use sotran04 in 0 again shared" , then when needed again somewhere in the coden i used "select sotran04 in 0", i tested and it is working
Thanks

 

[mlefkowitz]

Re-boot the server will fix the immediate problem. If your external application that uses SOTRAN has a file or record locking problem, then you must fix that or you will have this problem again.

Matthew Lefkowitz
Lefkowitz Systems, Inc.

http://www.lefkowitzsys.com

 

[titoneon]

Hi Matthew
in the startup.prg file of the external application, where i am using the sotran.dbf file, i have "SET MULTILOCKS ON", should i replace it with "OFF" ?
Thanks

 

[mlefkowitz]

If you need SET MULTILOCKS because your application must lock multiple records simultaneously, then you must keep it. If your application does not lock multiple records, get rid of it. This command is probably not your problem.

Make sure you close this application before doing system tasks such as clearing locks and reindexing.

Matthew Lefkowitz
Lefkowitz Systems, Inc.

http://www.lefkowitzsys.com