Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Its too late for VFP 7 - but suggestions for VFP 8
Message
From
24/06/2001 22:53:05
 
 
To
24/06/2001 21:45:20
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00522770
Message ID:
00522926
Views:
9
Steve,

>>
>>INTELLISENSE IMPROVEMENT - ability to popup properties of objects created in the editor window something like: oObj = CREATEOBJECT("ADODB.CONNECTION"), then, entering oObj. it pop-ups whatever properties available. It is available in the command window but not the Editor window.
>>
>
>Is that true? If so, that is pretty lame.

Well, think about it a little. On the command line the object is actually created. In code that's not the case. It would surely be nice to have, and perhaps we'll see it in a future version and in VFP7 you could check the syntax in the command window, but I'd think that it would be fairly tricky to do in an editing window.




>
>>OO MENUS
>>OO REPORT WRITER
>
>Probably won't happen...as for reporting, Crystal Reports will probably be the best route in the future.

I'd agree with this.

>
>>OPTIONAL NATIVE COMPILER
>
>Will never happen...use VC++ for that, and be glad VFP is not going to rely on CLR. :)

You know, I think there's an outside chance we could get this in a future version. You'd probably need some sort of compiler directive that would be on the order of SET MACRO SUBSTITUTION ON/OFF where the compiler could check to see if you're using '&' or other p-code-dependent type commands. That and making sure that all variables and their types were pre-declared ....
Best,


DD

A man is no fool who gives up that which he cannot keep for that which he cannot lose.
Everything I don't understand must be easy!
The difficulty of any task is measured by the capacity of the agent performing the work.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform