David,

That is not my decision to make. The two projects are huge and would take many man-hours to convert, and we have too much to do already. As I said, they use Stonefield DataDictionary and ApplicationDictionary. If you are familiar with these, you'll know that they use GenScrnX in the screen generation. When you try to open and build the project, it generates a load of Objects for the screens. Each object becomes a group with one member. (command button group, text box group, etc) I quickly ran out of hard drive space before the project was half converted to VFP.

I have found a problem in the project file itself, where memo fields were sometimes pointing to D:. I thought we had eliminated that problem long ago. I copied the project again from the server and tried again, and after all the bad paths were changed to C: it built ok. Before that, I'd have to put a CD in the D: drive. I had forgotten about that since we no longer had it happening to us. However, I still am having a problem. The screens seem unresponsive. I'll keep hacking away at it.

Dana

>Dana,
>
>Have you just tried running the FPW 2.6 source code under VFP? About 19 months ago before MS released the patch, I was able to do this for one large project where they didn't want to do a rewrite.
>
>You really can't continue development in the environment, but frankly it's time to move the system to VFP object-oriented code and get away from the Y2K problems in the 2.6 code.
>