Hi Rick,

Looks like you and I have had very different experiences with ActiveX and VFP. I've always been surprised at how easy it was to write an ActiveX control and use it in VFP. I use ActiveX controls written in C++ in my apps and have never experienced any problems with them, and so far they have all been visual controls.

I'm not sure why you say that a VFP form is not a standard windows form? It appears from what I can see to be just that. The controls drawn on it are not standard windows controls, but the form itself seems to be a standard Window that has been subclassed. When I add an ActiveX control to the form it also gets a standard windows handle and is what appears to be a standard windows object.

>>you're asking the equivalent of hosting a Windows form in a DOS application. Did that work? I don't think so...

Windows 1.0 through 98 was a DOS application <bg>

I do know what your point is, but I disagree that the challenges are of the same order of magnitude as you state. On the other hand I could easily be wrong about that.

This section is here for us to tell the VFP team what we would like, or what we feel would be useful to us. This is something I could use. I certainly wouldn't bet the farm on it, and it really isn't by any stretch of the imagination a critical feature for me, or one I think I would make heavy use of.

I think it's up to the VFP team to decide if it is a feasible idea and if it's a feature that they even want to provide. They have a lot better understanding of the inner workings of these systems than either of us do.

>>My personal opinion of all of this is this: Choose one or the other (.NET or FoxPro) as both have strengths. But using both together other than for transitional purposes is not something that I would bet the farm on for a variety of reasons.

Totally agree. Both are good systems and both have there own very different sets of strengths and weaknesses. .NET is not an option for 90% of the work I do, but there is tons of other type of work for which VFP really wouldn't be an option, so it swings both ways.

There are times however, such as the ActiveX controls I write, where being able to mix the strengths of two systems is a useful technique.

Truthfully... There is a bit of "I got this free copy of .NET with my VFP subscription and was hopping to see if I could do something fun (and useful) with it. <bg>" going on here. It's a new toy for me and I wouldn't mind playing with it. Where that would lead in the long run... I don't really know.