Critical errors in that number range tend to be related to a corrupt index file. I'm surprised that the data integrity check ran clean.

When do you get the message? Is it when you open the program, when you try and post, etc? Also, have you been able to print/post any batches since the move to the Windows version? My feeling is that the data will have to be repaired, unless you have a backup prior to the attempt to post.

If you are able to enter the program without getting the message, you may be able to save the batch. Open the invoice batch window and archive all of your batches and close the program. Then rename the qib* data files in your data directory (they are open batch files and batch control files- it's best to change the file extension), and finally open the program again. New batch control files will be created. Restore the archived batches and then try to post. If you are successful, then the problem lay in the batch control file. If you are unsuccessful, then the problem is elsewhere.

Also make sure that you do not have any extra files in the data directory of type qib####?.dat, where #### refers to a batch number and ? is either I or R. IF you only have a single batch number 100, for example, then you should only see the data files qib0100I and qib0100R. Any other files with different numbers do not belong (ie have been left behind due to an improper data restore procedure) and should be removed.