I ran into something like this when I noticed that the ncodepage field in the CoreMeta.DBF was blank for the table records ("T" in crectype). So while the tables on the users' system had updated code pages, SDT thought they were "wrong", so it fixed them, and then VFP put them back! I did a "batch" update and fixed it. Note: You may need a different Codepage value.

USE COREMETA
REPLACE all ncodepage with 1252 for crectype="T"
USE

Then SDT only fixed and reindexed all the files just the first time I put out new files, and now it just does the real tables that changed.

Rick

>Hi,
>
>Thank for your advise, I make a mistake as my original table already
>being converted to VFP free table when I modify their structure.
>So, I just converted my VFP free table to fox2x file format and
>SDT still work fine.
>
>BTW, why do we still see those form with progress bar when we
>do a SDT needupdate() function, follow by update() and reindex().
>Since my dbf files didn't change any structure but just had
>record append in, I thought the function will just check and
>not do anything, but I often see the progress bar and it taking
>some time with big table. I am doing those functions above to ensure
>those dbf are okay.
>
<snip>