nvarchar(max) vs. what was entered in Manage User Fields

[former_member313593]

When I create alphanumeric fileds in the manager user field function, all are being created in SQL as nvarchar(max). Then off course that causes problems with other tools such as Crystal.

I have a customer running MS SQL 2005 and Patch 45, this doesn't happen. I have another customer running the same (MS SQL 2005 and PL45) and they get nvarchar(max) on all alpha field adds. They both have their collate sequence set correctly, what other setting what cause this not to happen?

Thank you for any insight

[Former Member · Accepted solution]

Dear

1. While entering into B1 MSSQL is chosen : In this case the UDF created

will have a Data type of "nvarchar(20)".

2. While entering into B1 MSSQL2005 is chosen : In this case the UDF

created will have a Data type of "nvarchar(max)".

Hope it answers your question.

Best Regards,

Xiaodan AN

[Former Member · Accepted solution]

Hi, An,

But the Data type of "nvarchar(max)", can't be used as Cross Tab Report under Crystal Report !!

If so, I will need to write script file (Stored Procedure) for all related analysis report,

Best regards,

Michelle

[former_member313593 · Accepted solution]

I change the nvarchar(max) to the char(xx) as needed right in SQL. I've found so many issues with using crystal, sql queries, .net programming and other things that I simply don't leave nvarchar(max) fields out there. It just causes too much grief, trouble shooting and lost time.

I also have a routine that looks for user UDF's that are nvarchar(max) and sets them to what the Tools, Manager User Fields has them set at. It displays them first and then let's me change them, so I don't change any add-on's (ie. valogix) nvarchar(max) fields.