I have taken most of this response from another recent issue in this forum to do with unopen file units. Similar advice will apply here as well.

It's unlikely that a data integrity problem is causing this file unit error, and in any case, DataCare would not be able to fix an error of this sort; it's purpose is to find invalid characters in fields.

File Units represent data files and which user has access to them. For example, if someone is editing a customer, the file is locked, preventing anyone else from editing the same customer at the same time. If a problem occured while editing was taking place, the program may think a file is still in use when that's really not the case.

If DataCare actually reported a "File Unit x is not open" message on a specific application that it was supposed to check, then my thinking is that one of a few possibilities is occurring:

1. Another user's PC is in OE at time of the DataCare check (which I find not very likely, as DC would normally give a warning upon startup that it requires exclusive access in order to perform a check on the selected application(s).

2. The system THINKS that someone is in OE as a file has become 'stuck' so to speak and gives this impression when in actual fact it is not true. Sometimes rebooting helps this scenario.

3. The ezsemtabl.xxx has become damaged for some reason. If rebooting the system does not help, I would suggest you close the Accpac Plus WSM. Then, rename the data file ezsemtab.xxx (where xxx represents your data file extension) in the directory where your OE data is. When you next run OE, this file will be recreated fresh. The resulting DC check should then not report this File Unit error.

4. Should the error still happen, this may be related to the version of Novell Client 32 you have on your machine. Novell Client has been known to give File Unit errors in Accpac Plus programs in certain circumstances, where another version allows the same functions to work successfully.

Have you upgraded your machines or your network/client recently? If so, ensure you are using the most current version of Novell Client.

Hope this helps! Please update us if you got it resolved.

Regards
Softrak Support