any idea what this error message is please , someone has suggested that it was because people were logged in however everone was logged out and the server temp. disconnected from the network.
so I am stumped (which isnt difficult)
loks to me like the data you were trying to squirt in is of the wrong type, but I’m no expert in these things
With a bit of googling…
:google:
- Btrieve error 88
A Btrieve error 88 occurs when CLS tries to open a non-shareable file that is already in use by another process. It normally occurs when one of the temporary files used by CLS is accidentally left open.
If you are using the network version of CLS, the server (and all workstations) must be shut down and rebooted.
If you’re using the single-user version of CLS, try rebooting the workstation first. If that doesn’t solve the problem and your CLS data is stored on a server, then you will need to reboot the server as well.
One would think reading that above that you have a silly fatally flawed database system where workstation accessing it that does not close down in a normal manner F00ks it because a file is still classed as open and assigned to use and its not got the intelligence to reset the permissions based on a time out period.
88 - INCOMPATIBLE MODE ERROR
The application tried to open a file in an incompatible mode. If the first application to access the file opens it in accelerated mode, all other applications must open it in accelerated mode. If the first application opens it in non-accelerated mode, other applications cannot open the file in accelerated mode.
Which says to look at…
81: LOCK ERROR
This error can result from any one of three conditions. One cause is that the Btrieve lock table is full. Specify a larger value for the locks parameter of BSERVER. Btrieve also returns this error if the lock function call to the operating system failed.
Another possibility is that you attempted to unlock one record that was locked with a multiple record lock, and the record position stored in the data buffer did not correspond with any record that was locked in that file.
RED Interpretation:
The most likely cause of lock errors in R.E.D. software is attempting to run a program whilst another user is running a single-user option. Certain operations in R.E.D. packages are set up as single-user operations in order to speed the processes and also to ensure data integrity. Other users cannot use the package whilst these operations are in progress and the operations cannot be initiated when other users are accessing the data.