>Keith,
>
>Try these changes;
>
>Create indexes on DataPPO for Fed_taxid and Tax_sufx to allow optimization. You don't ever have to use these indexes yourself but Rushmore needs them.

I tried that, to no avail. Same dang thang >grrr<

> Then restructure your select to the one below;
>
>

>
>	?SYS(3054,2)
>	SELECT DataPPO.* ;
>			, ReimbrsKey AS OldReimbrs ;
>			, OtherId AS OldOtherId ;
>			, DtToCompJul( MaintDate) AS MaintComp ;
>			, DtToJul( MaintDate) AS MaintJul ;
>			, dmlError.dm_Link ;
>			, "K" AS StatusCode ;
>			, DataPPO.Tax_Sufx AS Old_Sufx ;
>			, .F. AS REPLACED ;
>			, dmlError.CODE ;
>		FROM DataPPO ;
>		LEFT JOIN dmlError ;
>			ON DataPPO.Fed_TaxId = dmlError.Fed_TaxId ;
>				AND DataPPO.Tax_Sufx = dmlError.Tax_Sufx ;
>                <strong>WHERE dmlError.Code = "120" ;</strong>
>		INTO TABLE dmoPPO
>
>

Tried that too. What this does, though, is filters
out records from the input file that don't have the
120 code. I need all of the records from the input
file, and just the matching link and code from the
error file. The where zaps any records that aren't
120's.

I've also tried changing the datappo & dmlerror in
the join match criteria.

I'm about to resort to a good ol' SCAN loop. :-|
I'm really curious as to why VFP (5.0) isn't
finding the right index tax though. I have a machine
with 6.0 loaded. I think I'll try it there to see if
there's a difference (but I doubt it). If I don't
mention it again I didn't see any change.

Thanks for your help.

...kt