Database User Error: -18

First, this is what we consider the legacy (older) DataPage, that is not a bad thing. It has been years since I've used it personally, and I don't know specifically what that error means, so please take this advice with a bit of caution. There are two things I can offer which might help.

DataPage gets its data from PC-DMIS via a file called XSTATS11.TMP in the PC-DMIS folder. MAKE A BACKUP OF THAT FILE, then delete it, and see if the next part update successfully. If it does, that file probably has some questionable content. There is a way to edit this file and clear out the "logjam" so the remaining data will process, but we won't get into that right now. If this procedure doesn't work, move on to the next step.

Its possible that the database somehow became corrupted. Find the database and MAKE A BACKUP OF IT before proceeding. You can use the editor to perform what is called an ASCII DUMP to save the data, then create a new database and do an ASCII LOAD to re-import the data. This procedure will exclude any data which is not valid, and may correct your problem. Once this is done, make sure you point PC-DMIS to the new database. Alternatively, you can replace the old database with this new one and use the same name.

These two options go a long way to solving many problems. Try this, but MAKE A BACKUP FIRST.

First, this is what we consider the legacy (older) DataPage, that is not a bad thing. It has been years since I've used it personally, and I don't know specifically what that error means, so please take this advice with a bit of caution. There are two things I can offer which might help.

DataPage gets its data from PC-DMIS via a file called XSTATS11.TMP in the PC-DMIS folder. MAKE A BACKUP OF THAT FILE, then delete it, and see if the next part update successfully. If it does, that file probably has some questionable content. There is a way to edit this file and clear out the "logjam" so the remaining data will process, but we won't get into that right now. If this procedure doesn't work, move on to the next step.

Its possible that the database somehow became corrupted. Find the database and MAKE A BACKUP OF IT before proceeding. You can use the editor to perform what is called an ASCII DUMP to save the data, then create a new database and do an ASCII LOAD to re-import the data. This procedure will exclude any data which is not valid, and may correct your problem. Once this is done, make sure you point PC-DMIS to the new database. Alternatively, you can replace the old database with this new one and use the same name.

These two options go a long way to solving many problems. Try this, but MAKE A BACKUP FIRST.