TimStone wrote:Silvio,
I likely have about 60 printouts, and they can be quite different. Each has it's own .prg.
For example, on any workorder, there are 3 options: Estimate, Invoice, and Worksheet. So in one .prg, as it goes through the process I mentioned earlier, it may print different data or formats. How does it know ? You can use IF ... ENDIF statements or the the good DO CASE option. You set an array of flags to .f., and then before printing you select the option you want for the format. That changes the value of the proper flag to .t., and the printout outputs those options.
If you requier multiple reports, you could first show a checklist. Then, you call a single Function that will print each report that is checked. You will need a key for the data to use ( in my case it is the workorder number ), but your reports can all draw the proper data based on that key.
To put it simply, each type of form has it's own .prg.
You start with a selection / options screen that allows you to decide which form(s) to print
The data for that specific job is then applied to each form and it outputs them.
Each form can have a unique design based on the needs and requirements of the client, or even the government.
Tim
Tim,
my intention is just this: I too should make many prg one for each print, I thought instead of building a dbf to store all the print formats.or example, on any workorder, there are 3 options: Estimate, Invoice, and Worksheet. So in one .prg, as it goes through the process I mentioned earlier, it may print different data or formats. How does it know ? You can use IF ... ENDIF statements or the the good DO CASE option. You set an array of flags to .f., and then before printing you select the option you want for the format. That changes the value of the proper flag to .t., and the printout outputs those options.
Each field should have the print condition
It is easy to say use ER or use quetaltra program, then we have to make a pile of documents to print and as you rightly say many have 3/4 different forms also according to the government provisions, here in Italy they have even modified document called "transport document alias DDT" which was simple to make it even more complicated.
At school, I am a practical technical teacher and for some years I have been seconded to the Technical Office, i.e. we collaborate with the school secretary for the supply of school materials (paper, records, cleaning materials, electronics, computers), so we have to dealing with suppliers.
If we have to buy an object we have to make at least 5 estimates and then to 5 different suppliers and then make the comparison document, since I did the program of the technical office (with fwh) the prints are obsolete and slowly I'm only redoing them that I broke my balls to make prints by hand and wanted to create something simpler in my spare time.
By now the view is not like it used to be and I get tired of building the print forms with the mouse and with programs that don't work and make you waste only time, these programs are good only for those who have to make few prints and who have a lot of free time to spend.
I am convinced that this procedure that I am creating is also useful to Mr. Otto (mod_harbour) because it is a dbf archive that can be modified and the function reads the format from the archive and prints the document