Specialization and Database in FM

[El_Pablo]

Hi,

I'm having a dilemma on designing a database. I would like to model an OO specialization.

There are multiple solutions in database theory to model this. Check here

Which one is best suited for FM? I should upgrade to FM10 by the end of the month.

Thank for all suggestion.

[Razumovsky]

I believe you can model all three of these in FM. I think you will find that the answer to your question has much more to do with the specific workflow and business logic of the scenario you are trying to model, and little to do with the application.

[Søren Dyhr]

What I come to think about are recursive structures:

http://jonathanstark.com/recursive_data_structures.php

...and then this one:

http://www.filemakermagazine.com/videos/data-tagging-classification-vs-organization.html

--sd

[El_Pablo]

Thanks Soren.

However in the first ling, I don't understand how the "lineage multikey" field works. What is the calculation behind this field?

Thanks

Nick

[Søren Dyhr]

I apologise the template migrated wrongly and by it defeats the object, the migration tool have cut some corners I weren't aware of:

Case(

DetailsControl = "Notes"; Contact_ID & "  Note";



Substitute(

Substitute("¶" & ValueListItems(Get(FileName) ; "Detail Types") & "¶"; "Note¶"; "");

"¶"; "¶" & Contact_ID & "  ")



)

What have happened is that one of the spaces in the double space in the first branch and the double space in the very end have turned into single space. Next migration typos was the pilcrow being stuffed inside the ValueListItems( def.

But all in all do you need to look at the layout of the hidden stuff, to see how the compound multiline is build. The technique

is the old way of building multi criteria relations up. Which means that the calc could be simplified quite a bit.

I enclose both the fixed original files set, as well as a new more up to date approach to optain the same functionality.

But by and large is what you need to know, what stacked values does when piled into a text field separated by a pilcrow (¶) ...it's an OR type relation, where the concatenated type seen in the original file is a bit of both AND- and OR'ing. What is written in the same line via a delimiter such as a space ...earlier on gave the AND'ing.

--sd

Migrationtypos.zip

Contemporary.zip