>Well, I thought I had it sorted. I compiled the app successfully a couple of days ago, got busy on some non-VFP stuff and when I returned to it, the same darned error came bacK!! I'm truly out of ideas on this. I can't compile ANYTHING. This project is seriously behind schedule (would be done in an hour or so if I could compile and test it!) and I'm supposed to be starting a major upgrade to another client's system on Monday.
>
>I must be missing something obvioius: the i/o errors are gone but there are still lots of DCOM errors, mostly from HP software for a printer that has been uninstalled but leaves registry entries and files behind (a known "feature" of HP software.) Is there some service that should be enabled that isn't? Other ideas?

I saw in your other reply that you're getting a strange .h error. Are there any 3rd party classes etc. that you may have purposely or inadvertently added to your project, that might reference that?

If you have any "real-time" or "continuous" backup software running, try stopping/disabling that for testing.

And do the same for antivirus real-time scanning.

Can you confirm you're running on XP, and with admin privileges during VFP work?

Do any CONFIG.FPW files or config files for VFP add-ons reference any drives or files that don't exist in your current configuration? I noticed your .h error was on a D: drive, is that another HD volume, optical drive, USB or ?

Back in the FPW days weird compile errors could come up if you didn't have the same configuration of drives available from one compile to the next. But, I think that's been fixed with VFP. However, it might still be worth trying - if when your compiling worked, you had a USB drive plugged in, and now that it doesn't, you don't, maybe you could try plugging the USB drive back in.