the corner office

of course, you could add something like

@IsUnavailable($Conflict)

to your select statement if you want to avoid conflicts.

btw, i've been meaning to go back and find something on your blog where you were talking about ViewNavigators and memory leaks in Java. wasn't that you? was it that you needed to specifically recycle the doc? i was wondering if this applied if you were just hitting columnvalues and never accessing the docs.

Oooh, that's interesting. On the one hand I want to say that IsConflict is an artefact of a view index, in that a replication / save conflcit is *always* presented the same way in a view (i.e. as a response, with the standard "Replication conflict" text taking precedence over all column formulae), but then I assume that this is in turn driven by the $Conflict field(s) in a document.<br><br>Hmmmm...<br><br>jonvon, this may be what you're looking for:<br><br><a href="http://www.e-md.co.za/web/colin.nsf/plink/040121-0224">http://www.e-md.co.za/web/colin.nsf/plink/040121-0224</a>

Hehe... the reason I'm pondering this is that I had overlooked the isConflict() function and was doing a hasItem() check on the document itself (long story). I had a doh! moment when I saw isConflict() in the Designer Help and decided to scrap my own li'l routine, and then I stopped and wondered whether isConflict wasn't doing in the background what I was doing in the foreground :)

Jon - on the memory leak issue, I'm actually not sure whether the document needs to be recycled if fields aren't read - good point - I'll test and see what shakes.

(Ben - if the first post didn't show immediately, it might be a lazy view reindexing problem that crops up intermittently on my server. I've retired one of your posts; sorry 'bout that :)

oh good, thanks (in advance) for looking into that colin! i've had a nagging worry in the back of my mind ever since you posted that!

thanks for the link too ben, i even posted another comment on that thread.

:-)