The more I use Domino 6, the more I grow to like the new features. Some of them really makes improvements to the way we can make websites stick together.
One of these features is the ability to include design elements on our forms from other databases. For example, you can include views and subforms.
Not all that glitter is gold though. At first I thought that embedding subforms from other databases would be a great way of creating modular designs, where the same layout was applied to several databases. That was until I found that you can't embed a subform from another database when that subform has other subforms nested within it! Even if the nested subforms are in the same database as the subform you want to include!!
Something else I don't understand is embedding views from other databases. It's a great idea but I don't really understand how it works, and I don't trust things I don't understand. Here the view embedding dialog:
Notice we can choose another database whose views we can select. The first thing I don't get is where this list of database is derived from. Anybody know? They aren't in my bookmarks. They are on the Workspace, but in no particular order and there are some in there that I'd forgotten existed.
The other thing I don't understand/trust is how the link to this embedded view is maintained.Note: This is really me being lazy. If one of you can help out, that's great. If not, I will endeavour to find the answer and let you all know.
Ok, so you've embedded the view from Database A in to Database B. Here, I assume, Database B remembers the location of the view using something like the Replica ID of Database A. If you then create a new copy of Database A it will still find the view. What happens though if you create a new copy of both databases A & B? Do you have to update the design of Database B to point to the new Database A?