>>>".prg" is not found!
>>
>>Is this one of the alternate errors caused by a bad PATH line in your
>>AUTOEXEC? There's a KB article mentioning a "DO dialog" that I think might
>>relate to this. I can't easily look it up right now.
>
>http://support.microsoft.com/default.aspx?scid=kb;EN-US;q163801
>
>I don't think that's it, but it's worth looking into.

Hey Garrett,

Don't work so hard.< g > Just do: MSKB#Q163801.