Sage 100

Error message - The Check Register data entry files are in use. Unable to update. Platform is MAS 200 SQL 4.50. MAS 20 server has been rebooted (kiiling pvxwin32s). Does SQL put a flag in a table to indicate files are in use? Nothing on the Sage KB. Next step is to call Sage.

It's not exactly what you write about here, but I thought I'd mention it (just in case it might help). I only know of File-->run-->glwska utility that will help if you get rid of Error: ""Bank code in use by another task"", ""Check Printing in Process"" or ""Other Check Printing in Progress"". This changes the check printing status in GL_Bank.m4t. Verify that no Accounts Payable or Payroll check printing tasks are open. If all printing tasks are closed, prior to running this.

That a very good suggestion and I hadn't considered it. Error messages are sometimes red herrings. I'll try that.

GL_Bank.m4t was not set for printing.

What about in manual check entry a ""Quick Print"" was not printed?

Good suggestion, Ruth. Perhaps also run all the AP registers. Also, I've had issues with Sage creating lock files in lock folders and not releasing them. For those issues, Sage had me change the name of the lock folder (I think, but am not 100% sure they would be named XXLock, where XX is the module abbreviation).

Myron, Can you tell me what task you are launching when you get the error message? my guess is AP check selection, maintenance, or printing. but can you verify?

Successfully able to print checks (this is not AP Manual Check), then when proceeding to print the check register, the error message appears. The SQL Profile trace indicates that the process fails when trying to access the GL_DetailPosting posting table. All other modules able to print the register and update.

based on the code, the message is triggered in only one place that I can find. My first thought is to look at AP_CheckRestart.m4t has anyone had you look at that table? Try to open it using data file display and maintenance to see if you get an error; also check in SQL Manager to verify that the table exists. I was looking at the code before your last post and based on your mentioning the SQL Profile trace trying to open GL_DetailPosting then I'm a little less optimistic that it is the right answer, but take a look at that file if you have not before.

When working with SQL. DFDM does not work with SQL tables. Must use SQL Management Studio. Premium also has a number of Providex files as well. THose are edited with DFDM Tables at not 100% SQL. I looked at the AP_CheckRestart and saw it was empty.

I can look at the code again tomorrow, but what about AP_DailyPostingWork.M4T this should be a Providex table and from what I can tell it is populated during all updates.