andrewBarker.com

New DB from template

OK, can anyone explain this one to me.

This morning I created a new database from a template to check on the settings for element level design inheritance. The template I used has many design elements identified with other templates.
I created a new db twice.

First time: In the new db dialog box, after I had selected the template, I left the "Inherit future design changes" box checked.

Result: All design elements had their individual inheritances blanked out. (And, obviously, the db level one was set.)

Second time: In the new db dialog, I deselected the "Inherit future design changes".

Result: All design elements had their individual settings remain intact.

Why would it do this? Is there a logical reason?
googlit:
ntf+template+bug
said: expand | collapse | rss

re: New DB from template (2006-07-10 09:57 AM by Chad Schelfhout)

re: New DB from template (2006-07-10 09:57 AM by Chad Schelfhout)The first time allows the new database to inherit from the template which would allow new forms, views, etc. to be added to your database and some removed if they where deleted.
The second database by unselecting inheritance you don't want any association with the template you just wanted to use it as a starting point. I think Notes is taking a copy of the template and since there was design element level inheritance it came along for the ride. This is how I would have expected Notes to perform.
When I am looking for design element information I usually make a new copy and unselect the ACL and documents. Then I know I am getting an everything just as it was.



Comments closed.
archives keyword index
by category ↓
by month ↓
ctrl - xperients


  • print (friendly)
  • font size: ∧  ∨
  • validations
syndication rss 2.0
Subscribe with Bloglines Subscribe with Yahoo