RE: BPCS 4.05 to 2.00

Wow!.

We were on release 2 something for several years then went to 4.02 (skipped
3 because it had a bad rep.), then 405CD...   Although 2.00 was a stable
release -- and I liked the way billing was handled then - this is a huge
step backwards.  I imagine  a lot of customization was done to it at these
other plants (hence the reason for them not moving to BPCS 4.05).  From my
own experience, I don't think the code in 4.05 CD is that different from
release 2.  I  would try pushing harder for release 4.05 (CD?), heavy
customization and all, especially since SSA/GT is trying to make everything
else compatible w/ this release.  I believe moving back to 2.00 is moving
towards eliminating BPCS all together, i.e., support, up-to-date feature,
etc.

DeeDee Virgei
Systems Analyst
Nelson Stud Welding, Inc.


 -----Original Message-----
From:   Jesse Salazar [mailto:jesse.salazar@trin.net]
Sent:   Tuesday, November 20, 2001 10:36 AM
To:     bpcs-l@midrange.com
Subject:        BPCS 4.05 to 2.00

Due to a merger and internal politics, one of our divisions is being forced
to migrate from BPCS 4.05 to 2.00.

Would like some feedback/advice on such a move.

Thanks.


Jesse Salazar Jr., CSP
Certified Systems Professional

Senior Programmer/Analyst
EDI Services Coordinator


_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
or email: BPCS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.