That pretty much sums it up, I have a field that contains a zero length field in SQL server and by the time the result is passed back through a procedure call and SPT query it is null.
Only noteworthy thing I can think of is the field is nvarchar(max) on the SQL side. I would ideally like to address this without wrapping the value in my report code with NZ as in a perfect world I am justifying jumping to SQL backend and this would represent one more change that has to be applied. Technically I/we would be migrating a number of databases with similar functionality and this would be one more change to all of them. I suspect it is more than this one field and may be in more than one place.
Any insights would be appreciated.
FWIW, my connection string looks like below with obvious substitutions.
Only noteworthy thing I can think of is the field is nvarchar(max) on the SQL side. I would ideally like to address this without wrapping the value in my report code with NZ as in a perfect world I am justifying jumping to SQL backend and this would represent one more change that has to be applied. Technically I/we would be migrating a number of databases with similar functionality and this would be one more change to all of them. I suspect it is more than this one field and may be in more than one place.
Any insights would be appreciated.
FWIW, my connection string looks like below with obvious substitutions.
Code:
ODBC;DRIVER=SQL Server Native Client 11.0;SERVER=MyServer\MyConnection,1433;Trusted_Connection=Yes;APP=Microsoft Office 2013;DATABASE=MyDatabase
