The VFP Report Writer is amazing compared to other development tools
I've seen, including my beloved Xojo. I've had to create my own report
writer that spits out HTML based reports just to get me close to what
VFP offered.
Another language command is the SCATTER NAME and GATHER NAME. The
ability to create an object with properties that corresponds to each
field of a record is incredibly useful. Especially when combined with
the TEXTMERGE command already stated earlier.
-Kevin
On 06/27/2019 08:51 AM, Johan Nel wrote:
Hi VFPers
I have asked this question on foxite too with very little feedback, so
I am asking it here too.
If you have to summarize the 1 or 2 features of VFP that you will feel
is a step backwards when migrating to .NET or any other platform as a
move forwards.
Looking forward to your replies.
Two things that was highlighted on Foxite:
1. Macro-compilation
2. Evaluate(<script>)
From a X# perspective the FOX release already has support for:
1. DBFCDX and readonly access for VFP specific FieldTypes (AutoInc,
etc) with full support planned in the foreseeable future;
2. WITH/ENDWITH, TEXT/ENDTEXT (partially implemented);
3. Macro-compilation;
4. Script engine that can make full use of the .NET framework.
XBase greetings,
Johan Nel
FOX Member: Friends of XSharp
https://xsharp.info
George, South Africa
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message:
https://leafe.com/archives/byMID/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
