Sage 100

Heads up -> Sage 100 2018 and Crystal Reports: SAP Crystal Reports 2016 for Sage (version 2016SP04) now ships with Sage 100. The following new features are included in this version: - Conditional formatting of boxes and lines, including the ability to conditionally suppress - Vertical text alignment at Top, Middle, or Bottom - A GetValueDescriptions function to display parameter value descriptions in your report layout - Direct data access for SQL Server 2014 You must **manually uninstall earlier versions of SAP Crystal Reports before installing SAP Crystal Reports 2016 for Sage.** The **SAP Crystal runtime included with Sage 100 2018 is not backward compatible with previous releases of Sage 100** If Sage 100 2018 is installed on the same computer as an earlier version of Sage 100, you must **copy the pvxwin32.exe.config file from the ..\MAS90\Home folder in your 2018 installation to the ..\MAS90\Home folder in the earlier version of Sage 100.** In an advanced or Premium installation, you must complete this step on both the server and the workstation.

This was something thrown into 2018 at the last minute, or at least it hadn't been in the previous betas for Payroll....Hope it all works out.

Exactly @BethBowers

Is this simply a case of copying the pvxwin32.exe.config to the old version of Sage and then both versions can run side-by-side? If so, it seems like mainly an issue for Advanced/Premium since you have to go workstation to workstation to do this.

Or if you have a million versions on your laptop, like most of us do. I'm wondering how far back it is compatible, because I still have to run 3.71 crystal reports every now and then. Now the weird thing is that loading 2018 on my laptop screwed up my 2017 and obviously the HOME folder is in two different places, so... I had not gotten this info and HAD to have my 2017 running ASAP so I had to uninstall 2018 and redo the WKSTN for my 2017. I could not JUST do the WKSTN for my 2017. But maybe I'm special.

Can the versions be separated by user profile? That may be a work around. A pain, but a work around.

I currently have VMs on the server for Crystal 8.5, 10, 11.5 and 2011. What's one more?? At least they skipped 2013...

That's what I was looking for, a VM - makes sense especially for trouble shooting.

Also, there is a conflict with Sage Fixed Assets v2018.0 in that it is using Crystal runtime version 13.0.19 and Sage 100 v2018 is using runtime version 13.0.21. It's causing errors and fixed assets article 86606 has the steps to fix the errors.

Glad to read that issue froms 10 years ago are still issues today.... So much for being a global company with products that integrate with one another.... I was thinking about putting off a v2017 upgrade later this month and go with v2018 instead (no PR or JC) but then I remembered that they have Sage Fixed assets......

I think this is the link with the issue that @ShariEckersley is referring to - https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=86606&sliceId=1&cmd=displayKC&dialogID=21394&docType=kc&isLoadPublishedVer=&stateId=21396&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

Carmen Cruz at Sage let me know that Crystal 2016 requires that all other version of Crystal be removed and will take it upon itself to do so if you don't do it first. Pretty much requires a VM. Attachment refers to the pvxwin32.exe.config file that needs to get copied to older versions.

I installed Crystal 2016 on my machine, had to remove the previous version. Then was unable to print anything in Sage at all. I then uninstalled crystal 2016 and reinstalled 2011 and still nothing would print. So finally I reran workstation setup and everything works. I can even use designer in v2018 of Sage 100 (even though my crystal is at v2011) so who knows. Hopefully no one else runs into the issues I did. For now - if it aint broke I'm not going to mess with it. It seems to me like they definitely threw this in last minute.

@NicoleRonchetti Did you (or anyone else) try [this](https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=86964&sliceId=1&cmd=¤tmsID=MS_Customer&docLink=true&isDocLink=true&languageId=&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl) yet? I'm hoping to get some feedback on whether this resolution cures instances where we are initially ""staging"" the v2018 program on the server. I'd like to start setting up 2018 to test on customer sites however I can't risk putting their system down even if it's for printing. This type of form compatibility doesn't seem like a huge problem but when you have 10 order entry and 5 shippers this becomes a very serious issue if people suddenly can't print one morning. **Cause** Sage 100 2018 uses Crystal Reports 2016. Some components are not compatible with older versions. **Resolution** - Rename the Pvxwin32.exe.Config file in older version located in the ""..\MAS90\Home"" directory on the server where the previous version of Sage 100 is installed - Copy the Pvxwin32.exe.Config file from the ""..\MAS90\Home\pvxwin32.exe directory where Sage 100 2018 is installed, into the ""..\MAS90\Home"" directory of the previous version(s) where the error is experienced. Note: If running Sage 100 Advanced or Premium, also copy the Pvxwin32.exe.Config file to Client-side workstation installation's ""..\MAS90\Home\ directory (i.e. where Workstation Setup was installed). #2018pioneer

@WayneSchulz Yes. I did have a problem with my old versions too, and the above solutions seems to have resolved it (so far). Its going to be a pain because I have a lot of systems on my local machine, I'll need to write a script to find/replace all of the pvxwin32.exe.Config files. I can't imagine having to deal with this on a clients system with a bunch of workstations. what a PITA.

The way that this is written it makes it seem that we can just modify the server and that will correct any older versions without going workstation to workstation. I'm a little bit skeptical.

@WayneSchulz ""Note: If running Sage 100 Advanced or Premium, also copy the Pvxwin32.exe.Config file to Client-side workstation installation's ""..\MAS90\Home\ directory (i.e. where Workstation Setup was installed)."" It does need to be done on each workstation unless on standard.

For end users on Standard - can we safely remote into their server, install 2018, move the file referenced above and expect that the users will be able to function normally on a pre-2018 version as we stage the latest release?

I just did a C: drive search for pvxwin32.exe.Config on a customer workstation with standard and it came up empty, so it appears that file is only on the server for Standard.

@WayneSchulz To answer your question about having both versions running, my experience has been that you can have both versions running (in my case it's v2014 and v2018) but you will have to make a choice as to which version you want to be able to print from. Even with Sage's ""fix"" of copying pvxwin32.exe.config to the v2014 installation, I'm running into Crystal issues.

Could this be a customized panel issue?