>I agree that two-way tools would be great. There are things that are easier done visually and others that are much easier in code. However, I find the implementation in VB has some serious shortcomings too. For example, if you have code attached to a form object and then delete the object from the form designer, all the associated method code won't be deleted. A similar problem is when you rename an object, then the associated methods won't work anymore since the name change is not propagated to the code. This is my (limited) experience with VBA. Maybe I'm missing something but this has surely caused me some problems.
>
>I think Delphi has better two-way tools. I always hoped that there would be some 3rd party tool that would allow something like ScxToPrg and PrgToScx. Interesting enough, SCCTEXT.PRG contains some comments about two-way support, but it's not implemented :(

I already mentioned that I considered the MS "implementation" of 2-way inferior to that of Borland/Inprise. In fact, MS does not "officially" support 2-way in VB or C. However, I do use it and with a bit of discipline it works for me. It's not perfect, but that is no reason for me to not use it at all.

There are "3-party" tools that perform SCX to PRG, PRG to SCX, etc. I built some myself; I use a VCX to PRG Converter specifically to make it easier to browse and absorb the VFP foundation and sample classes and as a final step in building my apps to reduce execution time and exe size.

It's the 2-way aspects and "seamless" integration with VFP I miss (ie. the way some of the other platforms handle it).

But while we're on the subject ...

It is quite possible that VFP was pulled from Visual Studio/.NET not for any "strategic advantage" that might accrue to VFP; it is quite possible it was pulled simply because it is a "hair-ball" to the Visual Studio IDE.

The Visual Studio IDE works great with Visual Inderdev, VB, C, C++, C#, .NET.

Why? Because they all use "text files".

It doesn't matter what the file extension is: .C, .HTM, .ASP, .BAS, ... The VS IDE handles it all, including (quite nicely) .PRG.

But it doesn't know a fig about VCX, SCX, MNX ... and probably never will.

It's quite obvious now that "Intelli-Sense" is table-driven ... in VFP and VS.

But until VFP discards it's "source *tables*" and embracess "text", ne'er the twain shall meet (again).