Null values in MS SQL after converting from Pervasive SQL

[nablainc]

I have a client who recently upgraded from Pervasive SQL to MS SQL. It seems that fields in MACOLA tables that previously had empty strings denoting "no value" now are null. I have had to modify Flexibility routines to allow for the null values, and many of their Crystal Reports require modification. Have others had this same problem when upgrading? Could this problem have been avoided when the data was converted?

Jerzy

 

[dgillz]

I have run into this. SQL does handle nulls differently. I would run file validation reports on all the major masterfiles if you have not already done so, and fix any errors.

The file validation reports are what I run BEFORE the conversion, to alleviate problems.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

"What version of URGENT!!! are you using?

 

[crystalreporting]

Checking on the option to 'convert null values to default' normally fixes any problems you might have with Crystal.

Peter Shirley

http://www.srhconsulting.com