Sharing techniques
Posted: Thu Dec 09, 2010 3:54 pm
At a meeting of the BRG board of directors today we duscussed, among other things BR, the possibility of sharing ideas, techiques and tips relating to existing features of BR as well as new features being added.
Some of this sharing might come from programs "ready to go" on a CD or thumb drive for BRG members, or simply posted here on the forum for anyone on the forum whether a member of the BRG or not.
To start this off I thought I'd share my technique for creating NWP/PDF forms that I can't steal from some existing place, like state or federal web sites. I recently picked up a payroll client in New Hampshire and will need to file New Hampshire unemployment tax returns quarterly. The on-line form is a two page landscape form that is odd sized. However the form that the department sends out for taxpayers to fill in and return is portrait and letter sized. Consequently I wanted the form.
Attached is the program that generates this form. The program by default creates the form as an NWP form using PREVIEW:/DEFAULT as the printer. To get a PDFD version simply un remark line 1140 and remark line 1142. change the file location for the saved PDF file on line 1140 to something that exists on your machine.
The program requires FNSNAP.dll that can be downloaded from the FTP site in the BRG_PUB directory as well as TT which also can be obtained from the same location. These file should be installed in a directory named "vol002" just below your starting directory (which is ofter "WB").
The purpose of the program is to show how I create forms and it makes extensive use of the functions FNPRINTNWP$ and FNPRINTBOX$. These are slightly different than the FNPRINTBOX that many of you have seen before (notice the $ in the new function name). They return a string that is then sent to the printer rather than actually sending characters and codes to the printer from the function. This methodology works much better in NWP, particularly with the ability to concantenante multiple instances of the function on the same line.
You should be able to just run the program, and then take a look at the code and logic. I hope this is helpful to you all.
FNGeorge
Some of this sharing might come from programs "ready to go" on a CD or thumb drive for BRG members, or simply posted here on the forum for anyone on the forum whether a member of the BRG or not.
To start this off I thought I'd share my technique for creating NWP/PDF forms that I can't steal from some existing place, like state or federal web sites. I recently picked up a payroll client in New Hampshire and will need to file New Hampshire unemployment tax returns quarterly. The on-line form is a two page landscape form that is odd sized. However the form that the department sends out for taxpayers to fill in and return is portrait and letter sized. Consequently I wanted the form.
Attached is the program that generates this form. The program by default creates the form as an NWP form using PREVIEW:/DEFAULT as the printer. To get a PDFD version simply un remark line 1140 and remark line 1142. change the file location for the saved PDF file on line 1140 to something that exists on your machine.
The program requires FNSNAP.dll that can be downloaded from the FTP site in the BRG_PUB directory as well as TT which also can be obtained from the same location. These file should be installed in a directory named "vol002" just below your starting directory (which is ofter "WB").
The purpose of the program is to show how I create forms and it makes extensive use of the functions FNPRINTNWP$ and FNPRINTBOX$. These are slightly different than the FNPRINTBOX that many of you have seen before (notice the $ in the new function name). They return a string that is then sent to the printer rather than actually sending characters and codes to the printer from the function. This methodology works much better in NWP, particularly with the ability to concantenante multiple instances of the function on the same line.
You should be able to just run the program, and then take a look at the code and logic. I hope this is helpful to you all.
FNGeorge