I've got a strange problem with the ORMSupportClasses. A couple of weeks ago it started with a problem with the designer in studio. I didn't pay too much attention on it but posted the issue on this forum a while back in this thread: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=7802

I tried some of the suggestions but can't solve the problem. It is a bit anoying but I still can work on the project, untill I stumbled agianst a "The size (2147483647) given to the column 'Body' exceeds the maximum allowed for any data type (8000). " exception in my project. I'm sure that this page worked perfect before. I had no clue where to start to solve this exception, so I searched this forum and found this thread: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=5635 That is exactly the problem I have (except I use an entitycollection based on a view in the DB) but that isue has been solved almost a year ago.

So once again I uninstalled LLBLGen and removed the RuntimeLibraries folder. I removed the dll's in my project and removed the references in the DBSpecific and DBGeneric projects. I reinstalled the latest version of LLBLGen and regenerated the project. This had no affect. I checked the version of the ORMSupportClasses dll in the bin directory of my web application and as far as I know it's the latest version. (file version 2.0.7.122)

I have no idea how I messed things up like this

Any help solving at least the second problem would be apreciated.

As this issue appears to be related to VS.NET 2005, do you have service pack 1 installed for VS.NET 2005?

That's what I thought for at least the first problem. But when I release the solution to the production server, I still get the "The size (2147483647) given to the column 'Body' exceeds the maximum allowed for any data type (8000). " exception.

I have SP1 installed.

That's a sqlserver error, you should make your complete record size < 8000 positions. So if you have 2 varchar fields of 5000 lenght, you can't have that in sqlserver 2000

I use SQL2005's nvarchar(max) datatype. I've specified a SqlServerDQECompatibilityLevel of 2 in the web.config

It only occurs when I try to page through a resultset. The initial fetch works perfect.

El wrote:

I use SQL2005's nvarchar(max) datatype. I've specified a SqlServerDQECompatibilityLevel of 2 in the web.config

It only occurs when I try to page through a resultset. The initial fetch works perfect.

THere's one issue with the CTE based query at the moment, where the resultset could contain duplicates because a 1:n relation + joinhint inner/none/left is specified, the CTE based query can't produce the proper page, so a temptable approach is chosen behind the scenes, even though the compatibility level is set to 2005. The ROW_NUMBER() based query should be build completely different which requires a new approach to how the query is generated so this is postponed till v2.1.

The temptable approeach apparently goes wrong in your situation, as it picks '8000' for maxlength and not 'max' in your situation, even though it can know it has to do that.

I'll fix this in the DQE.

I've attached a fixed DQE. Could you please test it to see if it fixes your problem?

Otis wrote:

I've attached a fixed DQE. Could you please test it to see if it fixes your problem?

That did the trick, thanks for the quick fix!!!!

El wrote:

Otis wrote:

I've attached a fixed DQE. Could you please test it to see if it fixes your problem?

That did the trick, thanks for the quick fix!!!!

Glad it's solved.

Is this fix in the latest 2.5 release? Or do we need to use the 2.6 version to get this working?

The fix mentioned here was for v2.0, v2.1 and higher should have the fix as well. Did you experiment a similar problem?

daelmo wrote:

The fix mentioned here was for v2.0, v2.1 and higher should have the fix as well. Did you experiment a similar problem?

Ya im getting the same problem issue. The version of the SD.LLBLGen.Pro.DQE.SQLServer.Net20.dll is 2.5.7.820

Here is the exception:

An exception was caught during the execution of a retrieval query: The size (2147483647) given to the column 'ContactNote' exceeds the maximum allowed for any data type (8000).. Check InnerException, QueryExecuted and Parameters of this exception to examine the cause of this exception.

It happens when going from page1 to page2. The ContactNote field it is referring to is varchar(max)

Please help me out. We have a major release due soon and to be honest, this issue is hurting us pretty badly.

Can someone please help with this issue? I have not heard anything back in some time. Is this an issue that other people are still experiencing with the lastest 2.5 installation?

I'll ping it back up to the developers to get it checked...

Matt

Sorry for the delay, it must have been accidently removed from the queue.

About your question.

The version of the SD.LLBLGen.Pro.DQE.SQLServer.Net20.dll is 2.5.7.820

The latest build for v2.5 is 2.5.07.1219 this bug was fixed on november 29th. please download the latest 2.5 version. Always do that when you run into an error, so we can at least rule out that it's a bug which is already patched.

That worked!!!