I had a bookmark set to launch a specfic nsf application at startup. It worked fine. Now I want to disable that auto-launching bookmark. I removed the bookmark programatically from my bookmark.nsf folder called $Startup. I can verify in designer that it is actually now gone from there. However I still have this nsf auto-launching and its still displays in the More Boomarks\Startup folder in the client UI. I need to resolve this programatically as I must remove this auto-launching nsf for hundreds of users bookmarks. Does anybody know what’s going on? If the startup bookmarks are gone from bookmark.nsf then they must reside somewhere else also?
On the Open menu, click the “More Bookmarks” folder. See if there is an entry under the sub-folder called “Startup”. This is what determines what applications will automatically start when Notes application is launched.
Subject: Removing entry from startup doesn’t stop it from auto-launching
Yes I realize that’s where the applications reside that auto-launch. When I manually remove an entry from “More Bookmarks\Startup” via the UI it removes the entry from the $Startup folder in Bookmarks.nsf and it properly supresses the auto-launch behavior.
Here is the catch - if I programatically remove the favourites document from the $Startup folder or permanently remove it from the Bookmark.nsf then the deleted favourites document continues to appear in the “More Bookmarks\Startup” folder and continues to auto-launch even though its entry was removed from the Bookmark.nsf?
I am confused. What else happens when manualy removing an entry from the “More Bookmarks\Startup” folder via the UI that I need to duplicate programatically in order to suppress the auto-launch behavior?
The other 2 places the information might reside is in desktop8.ndk and Cache.NDK. However, if you remove these, the bookmark still comes back which indicates that the information is only in bookmark.nsf.
From your description, it sounds like your removing the bookmark in UserBookmarkOrder within the bookmark.nsf’s design. The problem is that there documents which contain information about this bookmark and you are not modifying these. Unfortunately, the relationship among these documents in not part of a public API and modifying them will have unknown consequences.