Sage 100

 View Only

  • 1.  Crystal 2016 Compatibility Issue with previous Sage Versions

    Posted 05-09-2019 11:01
    @Wayne Schulz had previously said:

    My understanding:
    When you install v2018 to a workstation that also has a pre-2018 workstation installed - you will break printing
    • When you copy the pvxwin32.config on the server to the pre-2018 server - you will break printing for Standard users (not sure on Adv or Prem) unless they also have v2018 WKSETUP on their station
    • To work around this I plan to test on an isolated machine and don't setup 2018 on earlier workstations until go-live. At that time I advise they run all their tests on one workstation before     I go around and get all workstations uninstalled and install 2018
    • I have not done anything special on the servers when I install - I usually have 2018 in a folder alongside an earlier release. The 2018 seems to print fine and I usually am not doing the checking on prior releases so any inability to print from an earlier version on the server hasn't impacted me.
    • So far this has worked pretty well. It was really more of an issue before we had the feedback of what the problem was and the workaround.


    One thing I am not clear on - can you install Crystal 2016 on the server (with 2018 and a previous version) without breaking anything?​ Wayne says, "I have not done anything special with the servers" - Does that mean yes, Crystal Reports 2016 or just use the run-time to run reports.

    TIA

    ------------------------------
    Greg Stiles
    S & W Microsystems
    Torrance CA
    310.787.1010
    ------------------------------


  • 2.  RE: Crystal 2016 Compatibility Issue with previous Sage Versions

    Posted 05-09-2019 11:10
    Yes so long as nobody is working directly on the server in the earlier version.

    Yes so long as the server is not acting as a Terminal Server for users.

    Be advised that the same issue exists for 2019 (as it relates to upgrades from 2017 or earlier) except you must use the PVX configuration file referenced in the KB from 2018 as the 2019 version no longer can be copied/pasted to resolve the incompatibility

    ---------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ---------------------------------





  • 3.  RE: Crystal 2016 Compatibility Issue with previous Sage Versions

    Posted 05-09-2019 11:57
    Wow! Having such a hard time wrapping my head around this issue.

    @Kevin Moyes - "The problem you're referencing is the run-time print engine only, which is installed with v2018." - so installing Crystal Reports is NOT the issue, got it.

    "If a machine (server / workstation) has the new run-time version, it needs the updated config file to be able to print from an older version." - the server currently has Sage 4.5 AND 2018 Std, no one runs Sage from the server, no config file has been manually copied to the previous version - so if I understand this correctly, I should not be able to print from 4.5 from the server, but I can (preview and I assume print) - what am I missing?

    I guess I am not understanding what "If a machine (server / workstation) has the new run-time version...  /  ...does not have the new run-time version" actually means. Sage 2018 installed? 2018 workstations setup has/has not been run? 2018 config file copied to the previous version (appropriate path)

    @Wayne Schulz - No one is working from the server except me for maintenance. Not a Terminal Server. I saw all the latest discussions regarding 2019.

    ------------------------------
    Greg Stiles
    S & W Microsystems
    Torrance CA
    310.787.1010
    ------------------------------

    Original Message


  • 4.  RE: Crystal 2016 Compatibility Issue with previous Sage Versions

    Posted 05-09-2019 12:04
    I've seen really old versions not have problems printing / previewing with the installation of v2018.  It seems to be Sage 2013+ which causes the conflict.
    The CR runtime patch is installed with v2018 (server / workstation), but can also be installed separately (eg. installing a new version of Fixed Assets updates the CR runtime too, and you can specifically run the patch with a download link from the Sage KB article).

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 5.  RE: Crystal 2016 Compatibility Issue with previous Sage Versions

    Posted 05-09-2019 12:08
    If nobody is doing anything in the server you are good. I do my upgrades that way all the time.

    If you copy the config file to the older Sage then those workstations will need to run workstation setup for 2018 or they’ll get errors when printing.

    In short, So long as it’s just you on the server you’re fine except you won’t be able to print from the older Sage from that server workstation without doing the fix. In practice I rarely did this and just upgraded and worried about the compatibility only during go live.

    It won’t break the other users until you run workstation setup for their local workstation and 2018 pulls in updated Crystal. Then you’ll need to follow the fix suggestions from the KB.

    ---------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ---------------------------------



    Original Message


  • 6.  RE: Crystal 2016 Compatibility Issue with previous Sage Versions

    Posted 05-09-2019 11:10
    Installing the new CR Designer should not affect printing from older Sage. 
    The problem you're referencing is the run-time print engine only, which is installed with v2018.
    If a machine (server / workstation) has the new run-time version, it needs the updated config file to be able to print from an older version.
    If a machine (server / workstation) does not have the new run-time version, the updated config file will break printing from an older version.
    (Where the config file is placed to enable it for a machine differs from Standard to Advanced / Premium).

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



Related Content