Re: BPCS Docs

Thanx, I will take a look at it.
But, it is shoddy work that requires a 3rd party to make it readable.


fkolmann@revlon.com.au wrote:
> 
> > Yes, it is simple things (good programming practices) like putting VALID
> > TEXT and COLHDG on your database fields that would go along way in the
> > documentation effort.  Instead of having 8 fields called Date 8,0 use
> > those keywords to explain the function of the field.
> 
> As for COLHDGs there is a magic utility on  http://www.precosis.com.au/
> BPCS Column Heading Fix.  We have bought it and it works fine.
> It comes with column headings for all the BPCS files but you can alter then
> if you choose to.
> You can add your own files and change column headings, very useful if you
> have  included
> spare fields that you decide to use but dont want to recompile the file.
> 
> +---
> | This is the BPCS Users Mailing List!
> | To submit a new message, send your mail to BPCS-L@midrange.com.
> | To subscribe to this list send email to BPCS-L-SUB@midrange.com.
> | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner: dasmussen@aol.com
> +---

--
L. S. Russell Programmer/Analyst
Datrek Professional Bags, Inc.
2413 Industrial Drive
Springfield, TN. 37172
mailto:leslier@datrek.com
http://www.datrek.com
--
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---