>Once upon a time, there was a problem with developing code in FPW on drive D: when the app was run on a computer that had a CD drive D: holding no CD. The workaround was to stick in a CD, or to develop on Drive C:
>
>I haven't seen that error in years, and I do all my development on Drive D:. Suddenly, out of the blue on a VFP6 app, I have seen it twice in the last couple of weeks at the same site. Considering all the sites using the product with cd roms and no disc in place, I can't figure out why this is suddenly happening at this one site.
>
>Has anyone run into this using VFP6 lately? Any ideas (other than the obvious 2 mentioned above)?
>
Alan,

See if my FAQ#7872 might work in this situation.