Sage 100

Just a heads up, if you're installing Sage 2018 and migrating from a version prior to 4.50, you will need to perform an interim upgrade before migrating the data. I just got this message when migrating a 4.40 system. #2018Pioneer

Correct.

There's some type KB on this, though Sage's search makes it almost impossible to find twice.

I don't understand why this is. So we can upgrade no problem from say 4.40 to v2017 but not 4.40 to v2018. Does that mean Sage made an intentional decision for this?

Yeah, it's called ""blocking is cheaper than testing

It may be due to the Job Cost module in framework. We haven't had a module come to framework since Inventory version 4.40.

Not looking forward to new frameworks modules.. There goes the Upgrade budgets. Be careful folks!!

The training videos say it has to be v4.5.8

Thanks for posting that, @KellySappington.

And I just noticed this in the v2018 Upgrade Guide: ""If you are upgrading from Sage 100 version 4.40 or earlier, you must first upgrade to version 4.50 and install Product Update 8."" Our assumption is that you need to first upgrade to _at least_ 4.5.8, although it seems like it'd make more sense to just first upgrade to v2017, and then go to v2018.

Technically, it would seem that blurb in the Upgrade Guide should probably state ""4.5.7 or earlier"". And I suppose just slapping in PU8 might be better if running 4.5 (rather than going to v2017 first), unless of course you can't if for example enhancements are in play.

Does anyone have PU8 for version 4.50? I thought I had it, but only have PU7. Isn't there a site that 90 Minds members have access to where older versions of Sage 100 are stored? It seems like I've seen references to it, but don't know how to access it. Thanks

Probably in the Dropbox account. if you haven't requested access, you can do so by clicking on the link under the helpful links header (upper right corner

Thanks! I have access to Evernote, but will do the request for Dropbox.

Thanks Brett!

Just ran into this. Bogus.

Hi - does anyone have the release notes for 450 SU8 ? thanks.....

I have SU7 but didn't snag the one for SU8.

With enhancements not in play, are most of you first bringing the client to 4.5.8 or to v2017?

2017. I have a zipped file of a 2017 Standard install I copy where needed. I unzip to a folder (no install necessary), uninstall unnecessary modules, enter the clients registration number in System Configuration, edit the company name using DFDM, then do a chain migration. I keep it in place until go-live is done, then delete.

Doing 4.5.8 due to enhancements...

@BillPfahnl what do you DFDM - the registration name? I notice that doesn't change when keys swap so I presume that's what you are manually updating?

@WayneSchulz Correct. Migration doesn't change the registration name either so I change it in SY_System using DFDM.

Fyi, the system wouldn't let me install v2017 because v2018 was already installed, i.e.,: I _completely_ forgot about the '4.5.8 or higher' requirement for a 4.40 to v2018 Upgrade. Once I realized, I decided I'd first bring them to v2017.3 (rather than 4.5.8) since I'd rather work with the more recent v2017 software. But because I had already installed v2018, it wouldn't let me install v2017. I had to first uninstall v2018. Sounds like @BillPfahnl's solution above might have helped here.

@BillPfahnl when you do your interim 2017 migration without installing, have you used this process on a new server? I have found that if I copy an install on a new server, I can't launch it due to missing DLL (don't remember specifically which one). I have to have installed some version beforehand.

Hi @BarbaraGoldstein . Yes. You have to first install 2018 (or whatever the live version will be) before attempting to launch the non-installed version.

K, thanks!

Bill, these are my release notes for PU10, which show the PU8 notes as well. HTH