Wayne,

Are the Win2K machines up to date with SPs (SP3 is the latest). I believe that there were some known problems with cache management that were finally resolved with SP3. Not at all sure they related to .CDX files specifically though.

In addition, VFP7SP1 fixed some known problems with CDX content (not sure that it was specifically missing records) at the expense of doubling the CDX size once PACKed or REINDEXED, which is fixed in VFP8).

Finally, if these upgraded workstations are also new hardware, it may be possible that the HDs on the new hardware have on-board cache and this is ENABLED by default in Win2K. It is a good idea to DISABLE that feature if so. It can be done by going to the Properties of the HD and clicking on one of the pageframe tabs and UNchecking the appropriate checkbox. In Win2K SPs prior to SP3 this did NOT "stick" and had to be re-done between boots.

Oops - one more thing... reports here have newer NICs having power-saving features that has them turn themselves off if conditions apply. That sounds like an all-around bad idea to me, and I understand it too can be overridden though I don't know the steps to do so.

good luck


>Im having a problem with a VFP6 Application. We have recently upgraded some of the client machines to W2K, and now I have the same problem on 2 of the 4 W2K clients
>
>Ok..so here is whats happening. An INSERT INTO table MEMVAR command is issued, and the table is updated, BUT....the CDX file is not being updated. It appears to be nothing to do with file permissions, as I can point the data to a local data set with full permissions, and the same problem happens.
>
>I have tried recreating the CDX from scratch, and yes a reindex cures the problem only for the Index to go out of sync, when the next record is added.
>
>Can anyone point me in the right direction??