Sage 100

Not sure if I forgot this or never knew - inside the MAS90 folder is a folder called Lock. What is the purpose of the .LCK items in the folder and company sub-folders? Should they always be there, or are they supposed to be there temporarily?

From what I can see on our server, they should be there but be empty (0kb) if not actually locking anything.

The purpose is it allows BF programming to emulate a file lock and is a significant design improvement from legacy programming. During journal printing / updating at least, the CreateLock function is called and it creates the 0 byte .LCK file and physically locks it instead of locking the data file. This allows other MAS processes to know an update is in progress. When the journal update is complete, it unlocks the LCK file but not sure if it deletes it. There's no problem if you delete it yourself and if you don't delete, still no problem. In legacy when a file was locked during printing / updating of a journal, the actual LOCK command in ProvideX was used and this produced a real physical file lock on the actual data file and interfered. It was one of the causes of ""Table is not accessible"" when using ODBC to read records from a report or a business alert. Hope that helps.

Thanks for the responses. And I appreciate the explanation @AlnoorCassim. I am so glad you are part of this group!!

One other thing - have a client getting an error each week when they are selecting their AP check run (through Check Maintenance, not through Invoice Payment Selection). Support had me delete lock files and that stopped it for a couple of weeks. It's back and they are working on it, but just wanted to throw that out there. (Manually deleting lock files every week is not an acceptable answer to me, hence the reason they are still working on it.)

Sounds like the A/P check printing via Check Maintenance is not unlocking its own LCK files when its done with them. I'm guessing client is clicking on Print button in Check Maintenance to print Invc Pymt Selection Listing then clicking Yes to ""Do you want to print checks?"". That process is called chaining (and 3 points in the chain instead of the normal 2 if you had started with Invc Pymt Sel). Given how past check printing bugs related to chaining occur, I wonder if it works if they say No to print checks, then separately select Check Printing and Electronic Payment from the menu. It might be a better workaround than manually deleting the lock files

You are like our own walking MAS encyclopedia @AlnoorCassim !!!!

@AlnoorCassim - I'm going to have the client try what you say after I go clean up those lock files again. I actually had another client with the exact same thing but after deleting their lock files once I haven't heard back from them.

Awww shucks Barbara and Therese. I stayed at a Holiday Inn last night ya know.