Corrupt CDX Indexes

[gorepj]

I am plagued by corrupted indexes under ForPro 2.5a. Applications generate an unhelpful 'variable not found' error message that happen when indexes become corrupted. Inspection of the offending database show no index tag definitions. To recover we have to delete the associated CDX and manually recreate the index with the required tag definitions. These errors seem to spawn at random. How can I prevent them altogether?
Regards
Peter Gore [sig][/sig]

 

[dgrewe]

1. Start FP Filer (or WinExplorer) and look in all FP source code files for a line of code like "DELETE TAG ALL"

2. Look for some place in your code that copies the table and cdx to a temp location and only copies the dbf back to the original location.

3. If all else fails, post a code segment of what is going on in the application at the time of the error so we can see if there is anything we can find that could be causing it.

I have a routine that you can use that will reindex all files for you at night or when you need it. All you have to do is populate a table with the databases to be reindexed and the cdx tag info. I also have a routine that will populate the table with all the cdx info for you. If you want these routines, email me and I will give them to you. [sig]<p>David W. Grewe<br><a href=mailtoave@internationalbid.net>Dave@internationalbid.net</a><br>[/sig]

 

[ChrisCarroll]

If this is an 'untrackable' error not tied to any code, than we'd need more info:

1) How much memory and what OS on the workstation?
2) Are you running across a network, if so what?

We have had corrupted indexes which - after long drawn out attempts at solution - we think are caused by
(i) Network glitches
(ii) Problems in the NetWare client on Windows NT
and occasionally, user crashing at just the wrong moment.

Our solution is simply to reindex regularly, and take twice daily backups of data :-(


[sig][/sig]

 

[dgrewe]

Now that Chris answered, I remember one time I had a system trashing out indexes. The problem was a bad SCSI cable between the controller card and the drives in the computer. [sig]<p>David W. Grewe<br><a href=mailtoave@internationalbid.net>Dave@internationalbid.net</a><br>[/sig]

 

[compusolver]

Taking the 'variable not found' message at face value - could it be that you're using a system or other variable in your indexes ?

For example, using the system date (DATE()) variable will usually cause problems the day after you create an index.

Check the code in your reindex routines.

Hope this helps.

Hank Castello

http://www.foxprosolutions.com