Strange double entries in view

HCL Domino Domino Forum
1

I have two databases, one for properties and one for applicant to purchase properties.

Anyway, there are a couple of buttons that lookup the other database to see if there are any applicants for a particular property. The button code is:

@If(@IsError(@DbLookup(“Notes” : “NoCache” ; computer_server_name : MailingDatabase ; tview ; key ; 6)) ;

   @Prompt([Ok] ; "NOI not found" ; "No Notes of Interest can be found for this property") ;

   @Do(@Command([FileOpenDatabase]; computer_server_name : MailingDatabase  ; tview ; key ; "" ; "1" ) ; @Command([ViewExpand])))

i.e. the @Prompt is the THEN , the @Do is the ELSE with the relevant variables all defined okay.

The problem is when I include the @Dblookup to check if an entry exists in a view before I open it, I get a strange phenomenon.

The view it opens is a categorised (one category) on the other database and on previous versions of Notes client and Domino server, would scroll to the relevant point in the list, expand that catgory and show you the viewings for that property.

What happens now is that all categories are already expanded, although the aren’t really - the twisties are pointing right, but the contents are listed below. If you expand the twisties you get a document listed twice. It’s as if the cache for the view gets confused by the @Dblookup command that occurs before the @Commands. I’ve taken the @DbLookup out and it works, but then it doesn’t check for a valid entry before opening the database (which I want to do).

To add another strange element into it, if I open both databases before pressing any buttons, the formula works okay. It only happens if the button is doing the lookup and @commands on the database before it’s opened in the client.

Hope this makes sense. I’ve searched the forums here and can’t see anything like it. I wonder if anyone has encountered a problem like it?

We are running 6.5.4 and 6.5.4FP3. I’m sure we didn’t get the issue on 6.5.2. (I’m having diffculty getting the patch files to work for the upgrade to 6.5.5). I’ve had this issue on client 6.5.4 and on 6.5.5.

Thanks in advance for any pointers.

2

Subject: Strange double entries in view

I have no clue about those versions. But as a workaround, try these:

Have —> @Command([ViewCollapseAll]) in the ‘PostOpen’ event of that view.

Make sure that in the 2nd tab of view properties “Collapse all when database is first opened” and “Show response documents in hierarchy” are checked. And for ‘On open’, select "Goto top row’.

Please post if you see any difference with these additions.

3

Subject: Strange double entries in view

I’ve now upgraded one of our servers to 6.5.5FP2 and we’re still getting the issue, so perhaps it’s not release related (although I’m conviced notes 4.6.7 clients didn’t get the same problem).

Anyone got any thoughts?

anyone?

anyone?

4

Subject: RE: Strange double entries in view

Also…

If I F9 in the opened view, still the same problem. If I shift-F9 it fixes it, so there is something weird happening to the view index when I do the @DbLookup before opening the database.

5

Subject: RE: Strange double entries in view

Now. If I take the @commands out of the equation and just have:

MailingDatabase := mailing.nsf;

tview := “Viewers by Property ref”;

key := ref + " - "+ @Implode( address ; ", " ) + ", " + post;

@DbLookup(“Notes” : “NoCache” ; computer_server_name : MailingDatabase ; tview ; key ; 6);

Then I manually open the mailing.nsf on that view, I get the same result. The backend of the view being different or out of sync with what the server is showing me.

At least now I know that the @Commands having nothing to do with the problem.

Has anyone seen anything like this with @DbLookup?

6

Subject: RE: Strange double entries in view

A further update on this.

It’s something to do with the having “disable unread marks” checked for a database.

I was able to get the same problem using the discussion database template. I created two documents with categories 1 and 2. Then in catgory “1”, I made a button to do a @dblookup, then an @Command([FileOpenDatabase]).

It’s all okay without “disable unread marks”, but as soon as you tick this, the problem occurs.

Can anyone test on their server (doesn’t work on local copies for me) to see if they see the same behaviour?

Many thanks

7

Subject: RE: Strange double entries in view

I’m having a similar problem …

a have an agent that runs non-stop and checks if there are documents to work-on in a specific view. The agents does a getallDocumentsbykey to get the docs to work-on.

When i change the values of an existing doc to appear in this view, the agent sees the document and grabs-it. It then saves the document so it does not appear in the view anymore.

If i do this a second time whith the same doc, i can see the document in the view, but the agent does not see-it.

This is very weird … and yes, my agent has a view.refresh …