Hello;

I am trying to get a better understanding of how to best use LLBLGen. So far it seems like it can solve a great many problems I was having...

Say my application consists of 50 tables. I would load in all of the tables into a LLBL project. There would be some entites that represent a single table. Others entities would represent relationships between tables. I could leave the entities as they are by default, or I could trim the field selection down to only select out a subset of fields.

I could create entities that serve the purpose of representing related data for the purposes of editing it on a form. This could involve making entities that are customized from the standpoint of fields and relationships. That wasy when the form is filled in, I could call one SAVE() method and have the related tables updated. Would this be the proper thing to do?

I would generate code for the project. All of the code for all of the entities would be contained in one DLL. THis one dll can be referenced in my application and used to instantiate all of the entity classes. Is this a correct assumption?

Thanks in advance for your insight! Harold PS. It would be great to have a thread/forum on just Usage Scenarios. This would be great for beginners to read for ideas on how to best use this great tool!

Say my application consists of 50 tables. I would load in all of the tables into a LLBL project. There would be some entites that represent a single table. Others entities would represent relationships between tables. I could leave the entities as they are by default, or I could trim the field selection down to only select out a subset of fields.

Yes and no. All tables can be represented by entities, you choose to load the tables you need. Entites only represent tables, but relationships are maintained for all entites. You cannot trim the field selection down and retrieve an entity. Entities represent a record in the database. You can used dynamic lists and typed lists however to return smaller sets of data as datatables.

I could create entities that serve the purpose of representing related data for the purposes of editing it on a form. This could involve making entities that are customized from the standpoint of fields and relationships. That wasy when the form is filled in, I could call one SAVE() method and have the related tables updated. Would this be the proper thing to do?

You can have a form use entities and their properties which is related data to bind other controls on the form. Then just save the master record recursively.

I would generate code for the project. All of the code for all of the entities would be contained in one DLL. THis one dll can be referenced in my application and used to instantiate all of the entity classes. Is this a correct assumption?

Yes. You can also place the project in your solution so you could modify any of the customizable sections of the generated code.

Give the demo a try and post any questions that you may have while using the software.

Good Luck