Quantcast
Channel: Sage 100
Viewing all articles
Browse latest Browse all 36990

Forum Post: RE: Has anyone else had problems moving scripts to 2014?

$
0
0
Greetings, Without more details, it is hard to identify the problem but here are some suggestions. Is it only the CU_Person_BUS object which is having problems or is it all objects/scripts? If it is only CU_Person_BUS, then double check that the CU folder exists under the ../MAS90 folder on the server and that the CU_Person_BUS.pvc file is present in the CU folder.  If that doesn't exist then there was a problem with the install/upgrade as the Sage 100 CRM Module was not installed properly. If it is a problem with all objects, check the following: Was the 2013 installation also Sage 100 Advanced?  If moving from standard to advanced, there could be issues if the scripts aren't present on the server or for button scripts in Customizer if the run at server option isn't selected. You should also check that the Allow External access flag is checked in Company Maintenance for all companes that are running scripts. It could be that the nstallation path changed and that would affect any BOI scripts so check the path being used to init the script object (i.e. oScript.Init(PathHome)) in any BOI scripts. Thank you, Kent Mackall

Viewing all articles
Browse latest Browse all 36990

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>