I’ve got good news, bad news, and kind of good news.
First the good news. You can definitely do what you want.
Now the bad news, there is no real user interface for this, and it isn’t documented.
Finally, the kind of good news – you can set this up manually with the Field blueprint. Let me do exactly what you are suggesting with the HobbyShopSales vs. HobbyShopCustomers databases, linking the Email addresses in these two databases.
To get this to work, I just have to set up three items in the Field Properties blueprint – CLAIRVOYANCE, CLAIRVOYANCEDATABASE and CLAIRVOYANCEFORMULA. Here’s what they need to look like in this example.
- CLAIRVOYANCE - this needs to be on to enable the clairvoyance feature.
- CLAIRVOYANCEDATABASE - enter the exact name of the databasse you want to link to. The spelling must be exact, including upper and lower case. Panorama does not check, if you misspell the name it simply won’t work, without any error message or indication.
- CLAIRVOYANCEFORMULA - This must be the name of the field in the second database you want to link to.
You’ll notice that there is a CLAIRVOYANCELINK item, this should be left as “NO”. This item is used by the Relation dialog, you should not use it. (If you changed this to YES, the Relation dialog would “take over” the clairvoyance options for this field an override the manual changes you have made.)
The CLAIRVOYANCEFORMULA doesn’t have to be a field name, it could be any formula. For example if you wanted to link a field named Last in the current database to a field called Name in the second database, you might want to use the formula
lastword(Name). You can also leave the CLAIRVOYANCEDATABASE empty and use the formula to customize how clairvoyance scans the current database.
There is aldo a CLAIRVOYANCEVALUES option that allows you to completely change how clairvoyance works. If this option is provided, Panorama won’t scan the database, instead it will only scan the items provided. For example for a Shipping field you could use:
The example above puts each value on a separate line. However, if there are no carriage returns, it will look for commas, so this example could also be written this way:
As you can see, this is all quite powerful, perhaps even going beyond the “department of when is there ever enough.” However, it’s also quite complicated and unintuitive. It really needs a user interface to smooth the way. I haven’t figured out what that user interface should be, so I consider this feature to be unfinished, which is why it is not documented. However, it does work perfectly, and I do not anticipate that anything described above will change once a user interface is provided.
But wait, is this really enough? There’s actually a bit more. If you look at the blueprint for a text editor object, you’ll see that there is a
"$TextEditorClairvoyanceValues" property. This allows you to set the clairvoyance values for an individual Text Editor field, even if it is editing a variable! Again, there is no user interface or documentation for this (so far), but you can use the blueprint to set it up.
Ok … I think that’s enough!