Dear Rserao,

There are several scenarios that could cause you to get this message. The “Unable to open database - currently locked for integrity check” may imply that a crash occurred during an integrity check and files were left locked.

You said that you had re-booted the machine on which you received the error. However, if the software is on a network, simply re-booting one station may not solve the problem. Have all of the accounting stations logout, shut down and re-boot their stations. Doing this should close all of the files relating to the accounting applications as well as clean up other system resources such as which files and records are locked etc.
Start the station again and see if the error returns. If it does, let us know and we can look at other possible causes.

Hi Rserao,

If rebooting the workstation did not help, then my next suggestion is to get everybody out of Quik Check and all other Accpac Plus programs. Then look for a file 'EZSEMTAB' in the data directory and either rename it or delete it. When you next open Accpac or Quik Check for Windows, it will be recreated.

This EZSEMTAB file keeps track of which processes are locked, and if a computer has a 'hiccup', then this file may have been corrupted. If you are getting a Locking message when no-one else is in the data, then this would be the next step.

Error 533 is typically a failry generic message and could mean a number of different things. Usually it occurs when printing reports, but it could be due to incompatible Crystal files on that workstation, no batches to print, or some other possibilities (such as record locking). Also make sure that Opportunistic Locking is disabled on this computer.

Hello Ron:

I've tried to locate your registration by company name and/or phone number in our database. Would you be registered under something other than "CCNYI" and any imagineable abreviation of the full company name and its phone number?

Thanks

Another possible scenario that could occur in Quik Check for Windows (that has since been fixed in Adagio Checks) is the existance of orphaned batch files in your database. If data was restored incorrectly, some files related to open batches may exist in your data even though they shouldnt' be there.

First, open Quik Check and see which batch numbers exist. Then browse the data directory and look for files of a format QCC####?.DAT, where #### is a four-digit number related to the batch number, ? could be either D, H or I, and DAT represents your data extension. If you find files of this format with numbers other than existing batch numbers, that means you have extraneous files that need to be removed. When nobody is using the data, remove these extra files to a temporary directory, or simply delete them.

Well, that explains why I couldn't find you...

I know that someone from Cornell attended an Adagio webinar earlier this week. They should really move off this 16 bit implementation to Adagio Checks.

I trust you've found this support forum useful?

Hello Ron,

I'm glad you've found this forum useful. Would you have paid for the advice and problem solving?

Hello Ron,

Are you billing the client for your assistance? Are they saving money by not upgrading?

I know that "free" is always nicer, but for how long should "free" support be available on a product?

Use Windows Explorer and look for the files 'manually'. If you used the Search function and didn't enter the correct search criteria (such as your database not having DAT as the extension), the search may have come up empty when this really is the problem. If you scroll down the list of files, near the very bottom, you should see the QCC#### files. For example, if you have deleted batch 108, there should be no files related to this (ie QCC0108i.DAT). If there are, then this is a problem. Only OPEN batches should have existing files in the database.

Here's a link to another particular posting, regarding the batch listing and an error 533. I mention this one specifically because it came from another division of Cornell Cooperative...

Error 533 link

If you search this forum for 533, you will find about another dozen postings or so.
------
If the multi-user files are clean and there are no orphan batches, then I suspect either something new has been installed on your machine or something is wrong with your data. If you have access to Quik Check for Windows from another workstation, give it a try from there. Should this work, then there is a problem with the particular workstation.

Also try printing the batch listing report from the provided sample data in \softrak\qcwin\samdata. You may need to create a new batch if one doesn't already exist. Should that work, then the problem resides with your database.

Quik Check for Windows has been discontinued for a few years now, and we can't guarantee that it will work successfully on newer environments, such as Windows XP workstations or Terminal servers. It's replacement (Adagio Checks) is a fully 32-bit application with a better database interface, and the reports use a newer version of the Crystal Reports print engine.

Hello Ron,

Can you print a batch listing from the sample data? (softrak\qcwin\samdata\*.sam)