Hi all,
this morning I have found out that we have a db in our company, where the template db's "About" and "Using" documents correctly reflect the current version and description, but in both the Demo and the Productiv DB there are different "About" and "Using" documents. Our refresh cahin goes from the template db to the demo db and then to the the productiv DB. The DB was created by me in autumn last year and is apart from this problem very well thus the productiv db is labeled as 1.0ß, the demo is 1.0.1 and the template 1.0.2
My first idea was, of course, that the famous 'Prohibit desing refresh or replace to modify" switch would be on ... so I verified it , nada, no, nix, zero. It is not this switch. Well if it is not something inside ...
Someone else with similar problems or any idea how to solve it ?
Will now create copies of the databse to freeze this status and will update those 2 documents with Ytria in both, the Demo and the Produktiv DB.
Sincerly
Jochen "Joe" herrmann
Added info:
The DB was created with Notes/Designer 10 and I switched to 11 in early December
Did you try to replace design?
Hello Lars,
not yet , but will give it a try. Good idea.
As I am working in the home office, I usually have replicas of my template DB's on my local disk because its much faster.
These local template Db's replicat every hour automatically with our development server. I verified now the template on this server and ... it is also not replicating the "About" and "Using" documents.
I have created the copies and will now try replacing the design as Lars suggested.
Sincerly
Jochen "Joe" Herrmann
Ok, here my update:
I created a template file out of my template.nsf. This is because in our company we avoid to use *.ntf files.
Then I did a "Replace Design" and both documents are still unchanged.
My next try was to use a Blank.ntf and replace the design and ... both documents are still alive.
I assume that inside the design locks are, for whatever reason, activ and are not correctly displayed. I switched in the About doc design lock on and off ... no change. Will analyse now these documents with Ytria to see whats inside.
Would'nt these 2 documents a good method to keep a copyright statement or a customer name unremovable inside a db right ? Now I really want to know how reproduce this :-)
Sincerly
Jochen "Joe" Herrmann
Hello Lars,
I do not avoid *.NTF files. But in my current company they do, for whatever reason. I assume that they have made bad experiences with nightly automatisms ... but this, as said, is an assumption.
Sincerly
Jochen "Joe" Herrmann
Please forgive me my curiosity. I would really like to know why your company is avoiding ntf files.
Hello Lars,
welcome in the club :-)
Whomever I asked about this topic could only say that it was always like that. I can only assume that this developed long, long ago in another century and no one is left to explain.
In the past I have used several different ways how to organise the template DB, Test/Demo DB and productiv DB chain, and all used *.ntf's. Well I see it positive: I again learned another way that's working.
Sincerly
Jochen "Joe" Herrmann
The refresh issue might also be caused by a property that lets you inherit a design element from a different template than the main one that is set in the Database properties. Or if the design element has reader or author fields.
Another rare cause might be that the design element was part of a save conflict. Very rare and can also be hard to diagnose.
Hi all,
ok after several ideas and tries I found a solution, that now works for me:
I copied the content of the "About" & "Using" (called "A&U" docs from now on) documents into subforms to keep it for later. The I deleted the "A&U" docs in both DB's with Ytria.
Then I opened both DB's one after the other, to force Notes to create new emtpy "A&U" docs. These documents automatically have the "prohibit design refresh..." switched on, so I switched them off. Did this in both DB's !
Then I copied the content from the subforms back into the new empty "A&U" docs in the template DB.
And finally ... the design refresh worked again as expected.
But I still have no clue what was causing this trouble.
Sincerly
Jochen "Joe" Herrmann
I'm running into the same issue with trying to replace the design of the database and the "Using this database" document is not updating.
How did you disable "Prohibit design refresh" in this document? Can't seem to find a way to do that in the designer.
Usually with things like forms, views, agents, etc, you see the overall list of elements in a view and can see if a design element is protected.
No such view for About & Using documents though.
Hi Chris,
it's sometimes a bit tricky, indeed.
First try to select another design element where you have access to the elements properties. I usually use a form. Select it, not open !!! In Properties you should see now "Design Source
Inherit from the Design template ..."
Now select the "About document" and, voila, you should see what you were looking for.
Sometimes its necessary to use the menu option Window/Reset Perspective and then try it again as described above.
Check the status also in the DB's that derive from this db (Template ?)
Thumbs up!
Sincerly
Jochen "Joe" Herrmann
Bingo! Found it! It's working now. Thanks!