I have created a similar approach in .NET based on the NameValueCollection class.
Basically have subclassed it and added Methods:
1. ReaderToCollection - A SQLquery and a DBF to collection 2. ToSql - Construct an UPDATE/INSERT query based on the collection 3. ToControls - Populate a Form with values from the Collection
I am currently with some VFP users busy creating a tool that can read VFP Repos and translate it into VS X# Solutions/Projects. The Report Writer will be addressed once the other repo files are completed. As features are added to the VFP syntax support in X# it gets easier.
Johan
On 2019/06/27 19:25, Kevin Cully wrote:
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:
- Macro-compilation
- Evaluate(<script>)
From a X# perspective the FOX release already has support for:
- 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]