× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



<vendor>
Hi Jan,

This BPCS/ERP LX essay was written for you: www.unbeatenpath.com/up-a-notch/implement/debunk.pdf
It poses six provocative questions for an enterprise in exactly your situation.
The title on the document is: "Debunking Conventional Wisdom - Software Implementations & Version Migrations"
The content represents our cumulative years of learning about the process.

By the way .... Unbeaten Path developed a Y2K remediation product that employed the same patented 28 year fix philosophy that your company is using. We called it Resuscitator2000.
www.unbeatenpath.com/ads/R2000OxygenCylinder.pdf.
We have the technology to reverse the 28 year fix to prepare six-digit data for migration to eight digit fields. (MS4 went out of business not long after the new century got started.)

One of these days we'll have to start getting our product ready for the rarely-discussed Y10K problem.

With warm regards,
Milt Habeck
Unbeaten Path
+262-681-3151

</vendor>



----- Original Message -----
From: Roodt, Jan
To: bpcs-l@xxxxxxxxxxxx
Sent: Thursday, March 18, 2010 3:51 AM
Subject: [BPCS-L] Upgrade from BPCS 4.03 to BPCS 8.3


We are in the process of setting up a plan to upgrade from BPCS 4.03
(pre CD - running MS4) to 8.3.

Anybody through this process? Any suggestions on which route to follow
e.g. going to 4.05CD first etc. would be appreciated.


Regards
Jan


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.