DBFNTX/1210 Corruption Detected on Windows NT4.0 Workstation
Chris Wyborn
I have an application that uses 10 database files and about 25 indexes that
are all open at start up.
The app was previously running on a DOS/Win 3.11 system for the last 4
years with no problems.
I recently upgraded to a Windows NT 4.0 Workstation and ever since I am
getting random 1210/ Corruption detected error messages.
I also recompiled the app using 5.3b, CA Tools 3 and exospace.
These errors usually occur when trying to pack a database or seek.
I have tried to increase the number of file handles to 150, the old figure
used to be 60 and worked OK.
The rest of the app works OK, it is just annoying that these errors keep
happening randomly.
MN
I too get
>random 1210/ Corruption detected error messages.
to CDX indexes - NTX is fine.
I have tried 5.3b and things got worse.
I'll watch this thread with interest
--
MN
Don Andersen
On 4 Aug 1997 06:23:18 GMT, "Chris Wyborn" <a...@websurf.net.au> wrote
(possibly edited):
Chris,
Cannot help with a fix but, if you don't have access to it, here is a
copy of the NG file for Clipper errors:
[paste]
1210 Data and Index files out of sync
Explanation: Database (.dbf) and index (.ntx) files are not
synchronized, or there is a stack corruption or access problem related
to the RDD loaded.
Action: Some suggestions to resolve the problem are:
1. If the cause of this problem is that the database is being updated
through a utility external to the application, simply recreate the
index (.ntx) file and restart the application.
2. If the database was not updated outside of the application, check the
code for the application to ensure that all indexes are open when
updates are being done. Correct the code, recreate the index files
(.ntx), and restart the application.
3. Check that ALL index key expressions are a constant length. Usage of
LTRIM(), RTRIM(), TRIM(), ALLTRIM(), STR(), and DTOC() can all
produce expressions that are not a constant length. The TRIM()
functions should all be padded out to a constant width using PADR().
4. Use all three arguments to STR().
5. Use DTOS() instead of DTOC() in index key expressions. DTOC() is
dependent upon the SET DATE FORMAT.
Note: This error is applicable to the third party replaceable
database drivers (RDDs), and may not be applicable to CA-Clipper RDDs.
This may mean the stack was corrupted, preventing the application from
accessing the RDD's index expression. Increase the STACK or PROCEDURE
DEPTH. Look for missing or incorrectly ordered .LIBraries, or loading a
mismatched RDD.
See Also: Errors 1010, 1020, and DBFNTX/1210 in this chapter.
[end paste]
Don Andersen
Raf Verbeeck
I have had a similar problem but than with DBF/NTX.
The problem only occured when using data from a Novell server, when I used
Windows 95 and an older version of the 32-bit client software from Novell
(for Win95).
When I updated to the newest version, my problems were over.
Are you by any chance using Client32 by Novell ?
MN <M...@keysys.demon.co.uk> wrote in article
<BDvBzEAY...@keysys.demon.co.uk>...
> I too get
> >random 1210/ Corruption detected error messages.