Hi - have looked at other posts relating to above error but nothing seems relevant.
I have a @DbLookup on a web form that doesn’t work after putting some new design elements into the environment. It did used to work and does work on another server just fine. Works ok from Notes client too. I had this problem on another server a few days ago but the problem fixed itself the next day. I assumed the overnight processing fixed it so have run updall, compact, fixup, update and everything else I can think of.
Does anyone have any ideas on what else could be causing this?
It’s not common, but it is possible that one replica of a database among many doesn’t have the first column sorted correctly. (It has happened to me and no, I have no explanation.) Check the column sorting in the view in the “broken” replica, and make sure it’s not set to “None”.
Thanks for the suggestion - but the 1st column is definitely sorted correctly. Its even more annoying that the same issue on another server sorted itself out without explanation. Any other ideas?
Thanks for your suggestions. Unfortunately, the view issue was a red herring, and the problem was down to the authority to see the documents in the view.