SNIP
>Removing the data engine would also pave the way for the VFP language to be included in .NET.
>
Uh oh! Heresy! :o) Then the only difference between VB and VFP would be the syntax... :o) Would MSFT still support it all or push all VFP users to VB with the next version of .NET?
I like Charles suggestion in this thread for a MSDE/SQL checkbox. In addition to that, I would like to see data connections controls for MSDE/SQL dropped onto forms (like in Delphi) to promote MSDE/SQL usage in VFP. I would even like to see two versions of VFP: VFP with its native IDE and VFP.NET. Now, how to design to run under either... Ok, I'm dreaming now...
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"