>>Mr. Rauh,
>>
>> Thanks for the additional info. on soundex. In fact I already included it but i'm using IDX file instead of CDX file, I rather add a COMPACT statement in my INDEX expression since i'm using IDX file.
>
>That's fine; just remember to always open the .IDX file every time you open the file where the field that you index with SOUNDEX() could be altered or records could be added or deleted, since failing to do this will result in the index getting out of sync with the table. All indexes in a CDX have the equivalent of the COMPACT phrase in effect IAC, so unless there's an overwhelming reason to keep the index in a separate file, it's generally preferable to use tags in a .CDX, so that mistakes in opening the .IDX file are avoided (remember that the existance of an index in an IDX is ignored unless the file was explicitly opened and the IDX activated for a query.)

Ed,

In regards to SOUNDEX(), have you found any discrepancies within how this function is working? I am using VFP 6 sp4 and have found that if you do a soundex on an address (i.e. 2322 Post Road), I get a return value of 2123. According to other websites on the SOUNDEX algorithm, the first value should always be a character (A to Z) and numerics should be ignored. It seems as if VFP is processing the numbers because the first character is a 2 in the returned value.

Do you know anything about this? It seems to be a pretty big bug.

Pat.