RE: BPCS Documentation

[Dennis Munro <DMunro@xxxxxxxxxxxxxxxxxxxx>]

Sure is interesting where my question has led us to. 

George (Sagen), if you get the poster and need some help with the Visio part
of it, I would be willing to volunteer.  I have the  5.0 Professional
version.

Al, I did find the DOC* programs you referenced.  I end up with an error in
the call to DOC200DI if I have BPCSPTF ahead of BPCSO in the library list
and if I remove BPCSPTF  I get a "validation check failed, contact BPCS rep"
message and it signs me off my session.  The program I am running is DOC130C
to change documentation.  Like you said, the rebuild had to be run before
they were visible.  Talk about doing something blind.

We are a C/S BPCS version so I would prefer not to put CA/400 on every P/C
due to the security issue that is raised plus it just gives BPCS one more
program to conflict with.  Windows is bad enough.

Al, your comment about "this documentation should be used as a reference
tool " is exactly what I want it for.  We also want to know what "codes" do
and what they mean and what are available - to be used as a teaching and
testing tool.

Dilbert's Words Of Wisdom:
"I love deadlines.  I especially like the whooshing sound they make as they
go flying by."

Dennis Munro    
Badger Mining Corporation
dmunro@badgerminingcorp.com <mailto:dmunro@badgerminingcorp.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
+---