UNSPECIFIED ERROR Custom Crystal Report

Question

The KB 89925 indicates this is an issue of a custom report created in a prev version. This is not the case This report was created in 2018 using crystal 2016. However I followed the resolution to change the number to a string and it screws up the whole report. This only happens on some workstations. The report works fine on others. We have uninstalled and reinstalled WS and have IT looking into other machine differences. Anyone else seeing this? We have other custom reports that use the same parameter {select month) that work fine. We have tried rewriting the report Sage support says go to Sage city??????

BShockley · Accepted Answer

If you make the appropriate changes to the selection formula, it should not adversely affect the whole report. What problems are you having after changing the parameter from a number to a string?

WagonmasterON · Answer

I was getting this error on several of my reports and as you mention, I converted all parameters that were numbers to strings. But once you do that you also need to change any formulas referring to that parameter to convert the string back to a number with tonumber(). I hope this helps.

dlcottet · Answer

I found the issue (I think) On the server and the one WS that got this error Sage 2014 was installed. The client keeps all the PR old stuff in the old companies for archive, Once I removed sage 2014 I removed 2018 and crystal and reinstalled and no problems. Look for older versions of Sage installed - The server which still has the issue says 
 DSN has architecture mis match between driver and application I cannot remove the driver and am working with IT to resolve this Thanks for the ODBC hint

Sage 100

UNSPECIFIED ERROR Custom Crystal Report

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING