I am having intermittant problems with fields defined as NVARCHAR(max).

Specifically, when navigating to ListAll.aspx for an entity that has such a field, I'm getting the following error: _The size (2147483647) given to the column 'Notes' exceeds the maximum allowed for any data type (8000). _

It's not every time, though. I can see the first page of entities on ListAll, but when I try to go to the second page it fails.

I do not think this is directly related to the entity as I can edit and view entities by changing the ID up in the browser location bar and view/edit entity 11.

I do know that the error happens after the last block of code executed in the generated code:

        protected override DynamicQueryEngineBase CreateDynamicQueryEngine()
        {
            DynamicQueryEngine toReturn = new DynamicQueryEngine();
            toReturn.PerCallCatalogNameOverwrites = _catalogNameOverwrites;
            toReturn.PerCallSchemaNameOverwrites = _schemaNameOverwrites;
            return (DynamicQueryEngineBase)toReturn;
        }

Stepping through the code using F11 gives me the above error immediately after this method (from DataAccessAdapter.ca) is executed.

To reproduce this error, just add a field with type NVARCHAR(max) and put 11 records in it. Browse to the second page of the viewall page's grid.

Cheers, -jc

This is a paging bug in the Sqlserver DQE on Sqlserver2005. Could you try the latest runtime libs (which have this fixed) ?

Otis wrote:

This is a paging bug in the Sqlserver DQE on Sqlserver2005. Could you try the latest runtime libs (which have this fixed) ?

i can, sure...which libs? for sqlserver or llblgen pro? is there a version i can check?

cheers, -jc

The fix is in the SqlServer DQE, however they're versioned on the ORMSupportClasses dll. The buildnr of the ormsupportclasses can be found as follows:

The runtime library version is obtainable by rightclicking the SD.LLBLGen.Pro.ORMSupportClasses.NETxy.dll in windows explorer and then by selecting properties and the version tab. The version is then enlisted at the top as the fileversion. It has the typical format as 2.0.0.YYMMDD, or starting in 2007, the format 2.0.YY.MMDD

This issue was fixed on January 29th, so any build after that date contains the fix. Please obtain the latest runtime libraries build from the customer area, v2.0 section.

Otis wrote:

The fix is in the SqlServer DQE

my apologies; upon further review your previous note made that quite clear.

the continuation of this thread is just further proof that one shouldn't request help on a technical forum while under the influence of alcohol. ;o)

cheers, jc

LOL

Hi Frans,

sorry to dig up this old thread, but I have the very same issue with LLBLGenPro v2.5, using the 5/oct/2007 release as well. Could it be a regressive bug?

Thanks, Stefano.

Hi Stefano,

You should SqlServerDQECompatibilityLevel to SQLServer2005.

<add key="SqlServerDQECompatibilityLevel" value="2" />

Refs: - http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=9297 - LLBLGenPro Help - Using generated code - Application configuration through .config files - DQE Compatibility mode(SqlServer only)

daelmo wrote:

Hi Stefano,

You should SqlServerDQECompatibilityLevel to SQLServer2005.

<add key="SqlServerDQECompatibilityLevel" value="2" />

Refs: - http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=9297 - LLBLGenPro Help - Using generated code - Application configuration through .config files - DQE Compatibility mode(SqlServer only)

Huh... Yep, that did it. Many thanks!