Sage 100

Working on MAS90 4.2 to 4.5 upgrade - went through data conversion. It appeared to finish without errors - when I go in I find that GL is still at 4.2 but all other modules appear at 4.5. We did a test and this didn't occur. Just an FYI - odd. First time I've seen this without some other type of error message (typically stopping during conversion. It's also maddingly frustrating for bigger upgrades where testing is needed before the final upgrade (and therefore in-place less of an option) that forms you setup are over-written during conversion. It seems that only the custom form folders are over-written (removed) and the form codes stay in place although when you attempt to access them you view the generic forms. It makes doing a separate test upgrade (a necessity for larger upgrades unless the customer wants to be down 3 days) must more time consuming and error prone.

I did a 4.2-4.5 upgrade this week and that happened on about half the companies they had (they had 20+ companies). In a few cases it was some other module along with GL, but always GL.

How did you resolve getting the GL to convert to version 4.5? I'm going to have a 4.2 to 4.5 shortly with about 20 companies.

Just clicked on convert yet again...

Just as Beth said - I just clicked again on the convert and it finished up. The quirky things I keep running into: a. Upgraded forms in framework modules (IM, PO, BM) overwritten b. PVXDAX error on some workstations c. Failing to run MASCRCW exposes possible issue with CRPE32.DLL when customer receives the ""do you want to convert"" and then attempts conversion but it fails because the DLL does not seem to be populated by the install These are all documented but can be time consuming to fix the onesie and twosie problems. Since most of my customers want to test the upgrade -- I have not been doing in place rather I continue to do parallel upgrades.

Wayne, the forms are being overwritten even when you specifically say NO to that option? This is on the subsequent migration?

I say - no to re-migrate system files and yes to re-migrate existing companies.

I always copy the MAS_XXX\Reports folder BEFORE remigrating as a backup.

I thought there was an option for Crystal Reports and VI jobs (if VI exists)

VI jobs are in the system files but when you remigrate company data, the company-specific Reports folder(s) get overwritten at least in my experience.

The only time I""ve had the MASCRW fail is when I forget to update any non-BF UDFs before attempting the Crystal conversion. Also, just had someone with a SWCOCX 140 on a 4.50 - fix from Sage involves environmental variables (that didn't work) and renaming the CRPE32.DLL. This system did not HAVE any CRPE32.DLL in the System32 or SysWOW64 folders so I copied it into both and that fixed the error (only occurs with non-BF forms, I think).

Beth I just did a 4.5 upgrade from 4.3 where I had to manually copy CRPE32.DLL for every workstation. The problem appeared when they went into form that needed to be upgraded - they'd receive the ""click here to upgrade"" then a missing CRPE type message. I was surprised that it happened on every workstation. I'm wondering if it's more of a widespread problem that only appears when a user is prompted to convert (which in some cases may be seldom of you MASCRCW ahead of time).

My client's problem was the job cost invoice. Now it already said it was on 4.5 if I pulled it up in Crystal and looked at it, BUT on the invoice printing screen it said it had been created with an old version. But it never did actually ask her to convert. Her machine was Win 7 64 bit, if that makes any diff.

I think I had a mix of Win 7 - 32, 64 and perhaps an XP machine. Can't really put my finger on what could have been the issue other than I do not think I ran MASCRCW as sometimes if there are few reports I just allow people to answer ""Yes"" to the ""do you want to convert"" as my experience previously (until now) is that is often and equally quick way to fix these issues.