Hi

I upgraded to the new build and re-generated my code (i also changed some of the db struct and refreshed the llbl project) and when i run one of the pages i created previously i get the following exception,

[IMG]http://img137.imageshack.us/img137/7572/error8ah.th.png[/IMG] http://img137.imageshack.us/my.php?image=error8ah.png

Also not sure if it related but when i use the designer to setup the datasource two entries are listed for the datadapter.

Thanks

Richard

It looks like a version mismatch between the Database specific dll referenced and the latest database updates.

Make sure you generated your code against the lastest database updates, and make sure you reference the latest build of the Database Specific dll.

Also, it means that there are two fields with the same name in that same entity.... which is weird, as your screenshot shows that that's not the issue here...

Right an update, I tried to refresh the llbl project to the new db schema and that still came up with the error. Next i tried deleting all the generated code but still the error appeared.

In the end i managed to sort it out by creating a completely new llbl project and regenerating the code from scratch.

Not sure what the problem was but it would imagine that the llbl project had somehow got out of sync?

Thanks for your help

Richard

I've no idea, and also not seen this before. It seems that there were 2 or more fields generated with the same field index, which is weird. If it happens again, please let me know.

Hi Otis

Unfortunately i have got the same problem appearing again after i refreshed the catalogue and rebuilt my code. This time it is on a different field so there must be a problem somewhere!

I'm not sure how i can help here, would you like me to send the generated code and the llbl project?

Dick

I'm not sure how i can help here, would you like me to send the generated code and the llbl project?

Yes please, but prefereably in the helpdesk, open an issue and attach those files (zipped please)

You can also mail to support AT llblgen.com, and I will look into it a.s.a.p.

Emailed the code to get around the 512kb limit on the helpdesk!!

That's ok, I received it

This is an issue in the refresher. When a field changes ordinal, the field indexes could end up in a mess, as the routine which fixes the indexes after the refresh had the sort action also inside the loop, which of course needed to be placed outside that loop