Hi.
I’m sure there’s some post on this already, but I thought it best to highlight this problem again because I’m unaware of any planned fixes.
The functionality to embed views onto forms from other databases are great!
BUT…
The list for selecting the database from which the view will be selected is not making any sense. It’s cached somewhere and this causes problems. As a developer one has normally many environments to work on which in my case are controlled by switching locations. Notice that I’m still using the same Notes/Designer client.
When selecting databases, all the databases that has been opened (seems like) by the client shows in the drop down list. The developer has no way to tell on what server the database is located, this becomes a problem if there are multiple copies on different servers.
The developer should infact be able to program the selection of the database and it’s view alias. But since this is not possible at the moment I need to be at least be able to refresh the selection list of the database.
I’ve tried the following:
Any other suggestions or comments?
Does anybody know how and where the db list are cached?
thanx in advance
Subject: Embedding views headache!?!
The listing that you are refering to is a listing of all databases that you have opened up on your machine. This is saved in either the cache.ndk or bookmark6.ndk files.
There may be other places as well but I am not sure of were.
try deleting these two files located in the notes\data directory and see if that cleans things up for you.
Let us know what happens.
Ralph Borcherds
Subject: RE: Embedding views headache!?!
Thank you for responding,
I tried your suggestions, I presuming you meant bookmark.nsf instead of bookmark6.ndk.
Deleting the cache.ndk does not refresh the database list. However, if you remove the bookmarks db it migrates all the database icons from the workspace to your bookmarks, which in turn updates the database list.
There are still problems when working in a multiple replica environment. I’ve got 3 replicas of the same database, the id I use in designer has only access to the one server, in otherwords one of those replicas. I deliberatly changed the db name of the database to which I have access too. The name appears in the list but tries to connect to another replica when selecting it, which then fails. I then removed the other replicas from my workspace and it solved the problem.
The best solution here I think is to have the db selected by replica ID and supplying an optional server hint using formula language, and also when having to select manually, to provide the available servers in a list.
It looks like the same 'workspace db lookup’code is used here as when performing @Command([FileOpenDBRepID]) with no server hint.
Regards
Subject: I agree, this dialog box needs some help
When selecting databases we should be able to choose the server and then browse the directory path to select the database.
This is not only for embedded views but is in many other dialogs as well.
Howard