I am attempting to change primary keys on a table.

Originally it was a auto-generated int which has been deleted from the table. The entity was deleted from the LLBLGen entiies, and the resulting project files and re-added and code regenerated.

It recognizes that the old field is no longer there, but will not recognize the new composite key, it only takes the first field, an int, but does not recognize the second field, a smallint.

SQL Server does show the proper primary key as being a composite but LLBLGen will not.

Am I doing something wrong here ?

Dropped the table completely and created a new one with same setup and keys are recognized fine.

Something to do with LLBLGen internals when changing keys I guess. Creating a new Table and entity cleared it up

Which version of LLBLGen Pro do you use? (Date in about screen) as a refresher bug was fixed late 2004 which solved a bug in PK changes not being picked up, which caused dangling fields and an uncompilable project.

My bad.. I am on Vers 1.0.2003.1. I know I should upgrade but, well, I have no excuses, just sheer laziness masquarading as too much work to go thru the exercise.

So wht do I have to do to upgrade ?

Sink wrote:

My bad.. I am on Vers 1.0.2003.1. I know I should upgrade but, well, I have no excuses, just sheer laziness masquarading as too much work to go thru the exercise.

So wht do I have to do to upgrade ?

Log into the customer area, download the latest installer from the upgrades section, uninstall the older version, re-install the newer one, then open the docs and go to 'migrating your code' so see what you have to do to migrate your current code to the new runtime libs and templates. You have to re-generate and recompile all code. There can be some small issues with some breaking changes, but these are minor.