Empty = Empty? Workaround?

[Jeff Albro]

I did some testing, and apparently I can't relate records in two tables if I set two fields equal in the relationship and they are both empty.

Which is what I want.

I guess I need to set up a calculation that only enters "None" in both tables if there isn't already data in the field?

Is there another option?

-Jeff

[Søren Dyhr]

It's not very clear why you wish for such a feature, but you can move the auto enter serial to other side of the relation - you would just need to ignore the bird's-claw is going opposite of the one-many - it's still a one2many. The following lines in the "...allow creation of related record" portal recieves the first ever records serial number, even if the initial record later should be deleted.

Read up upon the feature:

http://www.databasepros.com/FMPro?-DB=resources.fp5&-lay=cgi&-format=list.html&-FIND=+&resource_id=DBPros000128

One cool use is that the primary key even can be a global, which then recieves the remote auto enter ... and exactly this feature have Bruce Robertsson cleverly utilized in a survey template here in this forum, which I unfortunately have lost track of for the moment.

--sd

[Jeff Albro]

All the records on both sides are already created.

Basically, I have two codes I need to relate.

Program Code and Subconcentration Code.

Program Code always has data in it, but not everyone has a Subconcentration Code.

The Programs table has both Programs and Subconcentrations in it. For a Program, the Subconcentration is blank.

So, if the program code matches, and there isn't a subconcentration code I want one answer for "faculty contact" but if there is a subconcentration, I want another answer for "faculty contact".

-Jeff

[Søren Dyhr]

I wonder if this is a many2many in disguise instead? Perhaps even a recursive ditto??

http://www.jonathanstark.com/recursive_data_structures.php

I still think there is no way around not being willing to serialize your records at all, but it's easily done via scripted replace! The use of human readable code is definitely a "no go" if the users have access to these fields.

--sd