Rick,

Thanks for the info.

For the printing, is it possible for the PDF file to be generated on the server and then printed directly on the user's printer with no action required by the user? In other words can a report just go directly to a printer without being presented on screen? Also, if that is possible can the printer be specified programatically so that certain reports print on specific printers?

Thanks again. Also, I have gotten through the first 2 chapters of your Internet Applications with VFP book and already have learned a lot. Thanks again for all of your contributions to the Fox Community.


>>I am working on a proposal to convert an existing FPD 2.6 application to become web based using VFP 7. I have concerns about how to make this conversion. I know there are frame works available to do most of this, but I have 2 major concerns/questions.
>
>This is a pretty wide open question. I think basically you'll be looking at a full redesign of your application. Your biggest task I suggest is building reusable business objects for your application so that you can easily use the app with different front ends. While you may not actually need another GUI app <g> it's a good idea to count on that in the future. It'll also make it easier should you need to share your data later on with Web Services in addition to the HTML interface.
>
>>The application will be used by 15 different distribution centers connecting to a common/central database. There needs to be security built in to allow access only to data specific to thier location, as well as allowing regional managers access to multiple locations. With a file server based application this is easy. What is the best way to track and maintain user security in this environment? Is it possible with a thin client application when the user does everything in a browser, or do I need to have the client running an application locally to help maintain the user information?
>
>Yes. Security can be handled in any number of ways from using NT security to setting up your own user accounts and validating against them. Once you've verified a user you can track a token to identify that user and based on that token you'll know whether he's validated. Usually the token maps back to a user account of some sort and from that you'd know what to allow. Sounds like you'll likely need this sort of setup that goes beyond what you can get out of an NT account.
>
>>The other question has to do with printing. Currently there are many functions that require printing loading/delivery information and other hardcopy reports. What is the best way to handle this? I know I can create PDF files for reports, but is there a faster way to just create reports and print them directly to a printer?
>
>You can use PDF and present them over the Web dynamically. There are tools like Adobe Acrobat, AmyUni and ActivePDF that allow you to print to PDF on the fly. You can then serve these documents to the client.
>
>>After over 15 years of writing file server type applications I finally have the chance to create an application in a new and exciting way and need to rethink the way things are done.
>
>Yes, it's very different, but not any more difficult than GUI apps <g>...