I have a page in a frameset on the client. The page has a hotspot. The hotspot is computed. The formula uses @GetProfileField to get a URL from a profile field.
This morning, I was having a problem where the client would lockup when the hotspot was clicked on or hovered over. I am not sure what I did but the (if I did anything at all) but the link started working and continued to work through the day.
The link started to cause the same lockup problem that occured earlier. I did nothing to the hotspot or the page.
I just made a change and kept the hotspot as computed but have a literal string to the URL. Not the optimum solution but it works so far.
A while back, I had a similar problem with a computed hotspot that used @DbLookup but, in my case, it didn’t cause a Notes lockup.If one of these hotspots was used in a Notes 5 client, in crashed the client.
In Notes 6/6.5, the hotspot had to be double-clicked for it to work - single clicks did nothing.
I got my solution from a technote, which said “To work around this problem place the @DbLookup formula in another field and reference the field from the popup formula.”
That solution may work for you.
I have also found a newer technote about your specific problem, with a different solution:
Only the first solution I described requires a field.
The second solution, in the linked technote, can be done with no fields. You just need a temporary variable in your link formula.
If that doesn’t work… I’ve found in most cases where I’ve used a page for something, a form works just as well. Just hide all the fields, and include a SaveOptions field set to “0” to make sure it’s never saved.