>We've recently had a disturbing number of indexes getting corrupted on 2.6 files. While I'm used to not trusting, say, clipper indexes. We rely on Foxpro indexes to be correct.
>
>The only recent change I can think of was getting two win98 systems for processing. Recently when reindexing a large file (3MM) on one of the new win98 machines, foxpro inserted hi-ascii characters after the tag name listed in the window echo. The actual tag was not effected, as far as I could tell, but it made me suspect win98 as the source of my problems.
>
>Anyone else experienced similar problems.
>
>The machines are also our first PII's (Pentium II, 300Mhz, 128RAM), which, by the way, are not always faster than our Pentium 150's. But I'd much rather blame Microsoft than Intel. The files are on a Novell 4, PII server, 100BT, all 3COM cards and hubs.

Hi Dan.

I did have a similar CDX problem when one of our remote sites used a P300 to re-create indexes using a foxpro 2.6 application. I had them re-create the indexes on their P133 system and all was fine. I recommended that they not use the P300 on the current app and wait till our VFP version is released.

There is a KB article out about Foxpro 2.6 and fast CPU's. Not sure what article it is. I'm sure you can search the UT and find a thread or two about it.

When working with 2.6, I use an AMD K6 200 with Win98 and have had no problems yet...

HTH

-Michael M. Emmons