Eric,
Thank you for your reply. I understand that report to ascii may be troublesome, but most of the report forms that I use are relatively simple and the only problem that I have seen is that lines and other graphical elements are left out. This just seems like a very simple way to output basic reports to html. I also use frx2word.vcx as another option.

I have found many great solutions to programming problems on UT, but I also look into the included VFP samples for guidance and when appropriate use the redistributable code and foundation classes to make my job easier. I also use sample code from this forum and FAQs, public domain code, purchase distribution licenses for third party controls when it make sense to use them and acknowledge contributing sources in the documentation of my applications. I have found very little that cannot be done with VFP. VFP itself has many good code samples as well as a large community of experienced developers who are willing to share their knowledge. I really am looking to validate that I am not misusing the tools that are available to me.

I notice in the help file, it indicates that some commands are not available and will generate "Feature not available" errors at runtime if used. I was pleased to find "modify report" was not one of these since I use this to allow the user to create and modify report forms at runtime. I have also noticed that several commands listed as unavailable are in fact available at runtime. Some of these include:

create view
modify structure

Because these commands are available, is it permissable to use them in code or from a runtime command line interpreter for maintenance purposes? I really would not want the user to have access to these, but I include a maintenance utility available to administrator level users and tech support that has a form that emulates the VFP command window.