Environment: SQL CE 3.5 SP1 (3.5.5692.0) .Net 2.0
Visual Studio 2008

LLBLGen Pro Ver. 2.6 Final (Aug 26th, 2009) SD.LLBLGen.Pro.DQE.SqlServer.NET20.dll (2.6.09.0729)

Hello,

I have been experiencing the same problem that was listed here...

http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=14397&StartAtMessage=0&#80433

and I have downloaded the fix that Frans has posted and I noticed that the file version for the fix is **2.6.08.1006 **while we are currently running 2.6.09.0729.

Before I apply this older version of the file I wanted to verify that this the correct thing to do. I always feel a bit weird when applying an older file version to fix an issue. If this is the case then I will need to make sure that we don't accedently update and break sometime in the future.

Related to this problem, if I target the .net framework 3.0 or higher (still checking to make sure all clients have necessary run-time installed) will this have any impact on the issue?

Thanks for the help.

no, please don't downgrade to that old version, please download the latest build from the customer area.

the version you have should fix the problem, but perhaps you ran into a different glitch. At least try the latest build and see if that fixes the problem or that the problem is still there, and explain in detail your situation, if it differs from the one you linked to

Frans,

Thanks for the reply. I did update the the latest build (file version 2.6.09.0917) and that did fix the issue. I had not tried that as the version I did have was already newer and was not working. Not sure why but I'm a happy camper now!!

Thanks again