>Ed & or Mike,
>
> Thanks for the help with the CHRSTR() thing but is there any reason why a machine would lock up when you use this command? I know this sounds goofy but I am replacing about 2 characters a record with about 98000 records..would this tank VFP. I am about to kill uper management and just wanted to know If I should plead insanity or Microsoft did it...Thanks
>

If there's an index on the field that you're updating, it's an expensive operation, especially if it's the active index. Try doing a SET ORDER TO 0 before doing the REPLACE operation. If there is an index on the field, you might try doing a DELETE TAG and recreating it after the REPLACE.