I'm curious if your accounting system source code uses the cobol report
writer. Gnucobol 2 rc3 doesn't implement the report writer. There is a
report writer version of gnucobol but it's not an official release yet. How
do you code your reports? What release of gnucobol do YOU use to compile
ACAS?
Some of the sub system do have a RW version of the report which I used
to work out how to use it however the original code is in the main
branch programs so no RW module is needed.
Why well I staring using it for all program compile and found various
bugs in the compiler that was not in the normal v2 branch so scrapped
using the RW branch moved all programs that had the RW coding in to
another directory.
This way all programs will compile with v2 or even for v1.1 at a pinch
(but I do not recommend using other than the v2 compilers.
When RW get merged into the v2 branch and this will be fter the v2.2 is
finally release and will then be called v3.0 I will rethink it but using
RW does not save much in lines of code so ...
In a nutshell all reporting is done using standard Cobol as used since
year dot - OK 1960-ish. So all programs are compiled even now using the
v2 RC code bases including from the source tree (direct).
One less series of bugs to worry about anyway.
Vince
On 15/06/17 03:13, John Grillot wrote:
I'm curious if your accounting system source code uses the cobol report
writer. Gnucobol 2 rc3 doesn't implement the report writer. There is a
report writer version of gnucobol but it's not an official release
yet. How
do you code your reports? What release of gnucobol do YOU use to compile
ACAS?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Addendum: Now that later Cobol compiler have been released of note is the v3.1.2 which is now production grade the usage of RW can be used.
How ever The most useful programs that could use RW are the one's that might need to be changed by the user / ACAS adminstrator and these are for :
Sales Ledger (Receivables) : Printing Invoices, Statements and may be reminder letters.
Mostly to allow these to be modified for layout depending on the user's reqirements where the printer specification is not a major factor i.e., all reports go to a text file and/or a .PDF file so that each one can be sent via post or via email.
The benefit of using email is you know it gets to the recipient as against using that old excuse of 'lost in the post'.
Purchase Ledger (Payables) for printing purchase orders, generating a bank pay list as a Bank to Bank payment etc but this one usually does not need to be in a special format
All other reports are for internal use and the layouts and headings do not require any changes.
Stock, GL / IRS likewise are also all internal reports although the P & L, Balance sheet and lastly Ledgers may need to go to the accountants.
So really four programs at most.
I will need to code up say the Sales invoicing program to see if it will make it easier for a user to modify the invoice layouts as against the current program.
Should point out that so far no one has asked for this type of work to be done nor requested help on changing these program to match up with any extra requirements above that already present.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm curious if your accounting system source code uses the cobol report
writer. Gnucobol 2 rc3 doesn't implement the report writer. There is a
report writer version of gnucobol but it's not an official release yet. How
do you code your reports? What release of gnucobol do YOU use to compile
ACAS?
Thanks,
John
Some of the sub system do have a RW version of the report which I used
to work out how to use it however the original code is in the main
branch programs so no RW module is needed.
Why well I staring using it for all program compile and found various
bugs in the compiler that was not in the normal v2 branch so scrapped
using the RW branch moved all programs that had the RW coding in to
another directory.
This way all programs will compile with v2 or even for v1.1 at a pinch
(but I do not recommend using other than the v2 compilers.
When RW get merged into the v2 branch and this will be fter the v2.2 is
finally release and will then be called v3.0 I will rethink it but using
RW does not save much in lines of code so ...
In a nutshell all reporting is done using standard Cobol as used since
year dot - OK 1960-ish. So all programs are compiled even now using the
v2 RC code bases including from the source tree (direct).
One less series of bugs to worry about anyway.
Vince
On 15/06/17 03:13, John Grillot wrote:
Addendum: Now that later Cobol compiler have been released of note is the v3.1.2 which is now production grade the usage of RW can be used.
How ever The most useful programs that could use RW are the one's that might need to be changed by the user / ACAS adminstrator and these are for :
Sales Ledger (Receivables) : Printing Invoices, Statements and may be reminder letters.
Mostly to allow these to be modified for layout depending on the user's reqirements where the printer specification is not a major factor i.e., all reports go to a text file and/or a .PDF file so that each one can be sent via post or via email.
The benefit of using email is you know it gets to the recipient as against using that old excuse of 'lost in the post'.
Purchase Ledger (Payables) for printing purchase orders, generating a bank pay list as a Bank to Bank payment etc but this one usually does not need to be in a special format
All other reports are for internal use and the layouts and headings do not require any changes.
Stock, GL / IRS likewise are also all internal reports although the P & L, Balance sheet and lastly Ledgers may need to go to the accountants.
So really four programs at most.
I will need to code up say the Sales invoicing program to see if it will make it easier for a user to modify the invoice layouts as against the current program.
Should point out that so far no one has asked for this type of work to be done nor requested help on changing these program to match up with any extra requirements above that already present.