Entities - ABCD Core Part 2 - Computer Learning Zone


	Back to ABCD Core Part 2 Comments List

Upload Images Link Email

Entities

Dirk Merkel

43 days ago

Hello everyone
I would like to ask for your input/opinion on the following...
I am "trying" to build a db for a our small company. We do the planning, building and servicing for sewage treatment plants. In the beginning I've had this idea to put all the plants in a different table and link it(M2M)to the entities (like customer, authorities,owner,operator etc..
Now, going though Ric's "ABCD", I think I would like to put the plants (being Entities) in the EntityT as well. I think it could be an easier way to handle all the different relations. But that also means I have to have two forms for the entities. One for Entities like customers and one for the plants (technikal entity).
one or two or more comments would be very much appreciated.
Regards Dirk

	Alex Hedley 43 days ago
Did you download the sample and try it out?

	Adam Schwanz 43 days ago
Should be fine, same concept as using a "HelperT" like Helper Data

	Dirk Merkel OP 43 days ago
That's what i was thinking. Just have to make a decision which way to go. lol so many possibilities. :-P I will try that version. Are there any videos on using 2 forms in one table?

	Adam Schwanz 43 days ago
That helper data might cover it, basically anywhere you use it you would just have to seperate the data, instead of just CustomerT for a recordsource, you'd have to do like Select * From CustomerT Where Entity="Customers" kind of thing (unless you wanted them both to be included on the form)

	Dirk Merkel OP 43 days ago
My 1st thought was adding the infos for the technical entities to the EntityT and create a second form like Entity2 (or tech) or something. Than when adding a new Entity choose Form 1 (person) or 2(plants). should work or am I getting it wrong?

	Sami Shamma 43 days ago
How many fields are you talking about? if they are few, then I will put them on the EntityT and have another "Tab" to maintain that data. That is what I do with my several versions of ABCD that I adopted to my customers.

	Dirk Merkel OP 43 days ago
exactly well not sure about the exact number of additional fields. not yet. If it gets too much I would go for a EntityDetailT or something like that. The question is "what is too much" It will definitely have its own tab.

Sami Shamma

43 days ago

There are several considerations
1- is your database split? If so, what is your backend? Is it access, SharePoint or SQL server?
2-are you running your database over a network?
3-if the table becomes too large, data retrieval will slow down significantly.
With those considerations in mind anything over 30 fields will start to become too big. But if all conditions are optimum, you might get away with up to 50.

This thread is now CLOSED. If you wish to comment, start a NEW discussion in ABCD Core Part 2.