Reporting
Posted: Wed Oct 30, 2019 12:20 pm
Maybe I have missed this somewhere ... how is reporting going to be handled?
Page 1 of 2
Reporting
Posted: Wed Oct 30, 2019 2:54 pm
Either by posting the report here, or using the "Tickets" button at the top-right of this website to open the report directly in GitHub. It helps reporting it here first if it's some matter that's worth discussing with other members first.
Reporting
Posted: Wed Oct 30, 2019 4:38 pm
Chris - I believe they are asking about Report generating in a VFP app. Report designer? Viewer? etc...
Reporting
Posted: Wed Oct 30, 2019 5:31 pm
Matt,
Robert already mentioned ReportPro as alternative and potentially make it read the VFP report files. The other option might be to try and compile the FoxyPreviewer with X# once all the VFP syntax/runtime features are implemented in X#?
I think you are correct.FoxProMatt_MattSlay wrote:Chris - I believe they are asking about Report generating in a VFP app. Report designer? Viewer? etc...
Robert already mentioned ReportPro as alternative and potentially make it read the VFP report files. The other option might be to try and compile the FoxyPreviewer with X# once all the VFP syntax/runtime features are implemented in X#?
Reporting
Posted: Wed Oct 30, 2019 6:43 pm
Hi IvyLeagueSoftware -
I can tell you from a reply Robert gave me in the VFP FOX Supporter forum that he thinks their Report Pro tool can be made to work with VFP reports.
Link to thread here: https://www.xsharp.eu/forum/private-vfp ... nnig#10661
I can tell you from a reply Robert gave me in the VFP FOX Supporter forum that he thinks their Report Pro tool can be made to work with VFP reports.
Link to thread here: https://www.xsharp.eu/forum/private-vfp ... nnig#10661
Reporting
Posted: Wed Oct 30, 2019 7:59 pm
not able to read private... but why not recompile the "stock" report handling added in vfp 9. which can be set as "Reportbehaviou 90" first? Sources to ReportOutput and Reportviewer (as well as ReportBuilder) are included in vfp. Is GDIPlus unable to run outside Win32/Win64 and foxyPreviewer has less difficulties running on Mono/Xamarin for Android ? PDF certainly more important than 12 years ago, but I guess foxyPreviewer will be harder to port...FoxProMatt_MattSlay wrote:I can tell you from a reply Robert gave me in the VFP FOX Supporter forum that he thinks their Report Pro tool can be made to work with VFP reports.
Link to thread here: https://www.xsharp.eu/forum/private-vfp ... nnig#10661
mused about the topic in:
https://www.xsharp.eu/forum/public-vfp/ ... list#11395
regards
thomas
att: readme and license from vfp reporting "90",seems permissive enough (IANAL!)
Reporting
Posted: Wed Oct 30, 2019 8:15 pm
Oops, right, thanks!FoxProMatt_MattSlay wrote:Chris - I believe they are asking about Report generating in a VFP app. Report designer? Viewer? etc...
Reporting
Posted: Wed Oct 30, 2019 8:29 pm
Thanks for the replys Guys.
Reporting in VFP | FoxPro
Posted: Wed Oct 30, 2019 9:42 pm
MainHatten said:
.
.
Here is the repo: https://github.com/VFPX/ReportingApps
I took a quick look at the source code it all appears in VFP code (PRGs and VCXs), and X#.VFP seems to be on a path to fully implement VFP code support, so this could look very promising, for someone to get this VFP report engine running in X# in pretty much the same way it runs in VFP.
Probably the most mysterious part of this is the _GDIPlus.vcx library that is part of the VFP installation.
The VFP Help file says this about _GDIPlux.vcx:
.
.
So, I did some looking around for these "Sources" and I see that indeed the VFP Reporting pieces are implemented in plain old VFP code, and are included with Microsoft's Visual FoxPro installation in a bundle they call "XSource", and I believe they open-sourced this XSource to the community when they announced they were not going to continue VFP (this may need to be verified). There is XSource.zip in the Visual FoxPro ToolsXSource directory... why not recompile the "stock" report handling added in vfp 9. ? Sources to ReportOutput and Reportviewer (as well as ReportBuilder) are included in vfp.
.
Next I discovered that Doug Hennig has put the VFP Reporting source code from XSource in a GitHub repo, and it has had many updates and revisions since the production release. So, anyone working with this should start from Dougs repo, not the one that shipped with VFP.Reporting Apps is part of "XSource", the source files for various Visual FoxPro components. The license governing XSource can be found in the XSource_EULA.txt included with all of the XSource releases.
Here is the repo: https://github.com/VFPX/ReportingApps
I took a quick look at the source code it all appears in VFP code (PRGs and VCXs), and X#.VFP seems to be on a path to fully implement VFP code support, so this could look very promising, for someone to get this VFP report engine running in X# in pretty much the same way it runs in VFP.
Probably the most mysterious part of this is the _GDIPlus.vcx library that is part of the VFP installation.
The VFP Help file says this about _GDIPlux.vcx:
.
So, maybe _GDIPlus.cvx is just wrapper code around Windows "stuff" and maybe once the code is finally down that GDI+ level, it can still run from X#, but I am not sure about that.The GDI Plus API Wrapper Foundation class library, _GDIPlus.vcx, contains a collection of classes that wrap GDI+ Flat API functionality for use in Visual FoxPro. You can use these classes to add GDI+ features to forms and reports.
Reporting in VFP | FoxPro
Posted: Thu Oct 31, 2019 1:08 am
Well, I have now learned that the source code provided through XSource is only run time items to build a report, preview the report, and then output the report.
There is no Report Designer; that is part of the VFP IDE, so that means there’s no way to create new, or edit existing FoxPro reports unless someone makes a new designer for it.
And since Report Pro already has a designer, it sure seems like the obvious path is simply for Robert to attempt migrating FoxPro reports to Report Pro.
There is no Report Designer; that is part of the VFP IDE, so that means there’s no way to create new, or edit existing FoxPro reports unless someone makes a new designer for it.
And since Report Pro already has a designer, it sure seems like the obvious path is simply for Robert to attempt migrating FoxPro reports to Report Pro.