Sage 100

#2018pioneer - Upgrading a client from 2014 Standard to 2018 Advanced. The plan was to only use a testing workstation for 2018. I ended up needing to install 2018 on the controllers workstation for testing thinking I could just uninstall and reinstall 2014. Not the case. After uninstalling everything, multiple reboots, the 2014 install is broken as far as printing/previewing goes. I resorted to calling Sage and their answer was a system restore. The Sage person I spoke to even went as far as to say he's been telling people to only go to 2017.

That Sage person needs to be fired! Copy the pvxwin32.exe.config file from the \HOME\ folder on v2018 the similar folder on v2014 (server and client) and you should be okay with printing reports.

Seriously, who do they have working in Sage support? Is there any training?

There's a Sage City on this - it discusses Fixed Assets but I think the concept is the same. https://sagecity.na.sage.com/support_communities/sage100_erp/f/sage-100-technical-and-installation-discussions/106634/unable-to-cast-com-object-of-type-error-in-sage-100-2017-after-installing-sage-fixed-assets-2018-1

Never call Sage before checking here first. Never. Ever.

The KB for front line support is very short. It consists of one entry, which suggests a system restore.

https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=86964&sliceId=1&cmd=displayKC&dialogID=702144&docType=kc&isLoadPublishedVer=&stateId=702145&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

@BethBowers. Perhaps a bit jaded!

It's all beta until at least service pack 2. Not just Sage, everybody...

Oh I did Check here. If I copy the pvxwin32 config file it breaks all the 2014 workstations that don't have 2018

The pvxwin32config fix worked for a 2015 upgrade for some reason. I don't know if part of the problem is that it's standard to advanced

Check the Sage City where it notes on some setups they had to install full Crystal 2016 to workstations. Doesn't sound like they had to do it everywhere but that some might have required it. I seem to require this quirk from the last time we had the Crystal version battlers.

Hello Kelsey - Also bear in mind that Sage 2018 uses Crystal Reports ""2016"" and Sage 2014 uses Crystal Reports ""2011"". If the ""old"" Crystal is still on the workstation you will be unable to print or preview

I don't know how to uninstall a runtime version of CR, but if possible that might fix your controller's workstation without a system restore.

Yes. It is the old crp32.dll thing - I bet Wayne remembers that!

If I uninstall everything (all client versions), reboot, and reinstall 2014 it still doesn't work. At this point, IT just gave her access to a different machine, just wanted to pass on the experience.

Due to the different versions of Crystal, it is going to be difficult to upgrade anyone that is not going live immediately.

Boy this makes it tough to pilot Test the new payroll and Job Cost.

The weird thing is that the Crystal change was really a last minute add. It wasn't until the last beta release that it was included.

I need to do something soon as all of the knowledge gained from the certification test is fast fading away. So if we install v2018, ANY workstation with the old version of Crystal needs to have it uninstalled AND pvxwin32.exe.config needs to be copied to EVERY previous install of Sage? is that the gist? Plus don't load it if are running Sage Fixed Asset?

I threw a question at Sage City to see if they can come up with a decent answer. https://sagecity.na.sage.com/support_communities/sage100_erp/f/sage-100-technical-and-installation-discussions/106662/upgrade-planning-and-the-new-crystal-reports