While I'm griping, how about providing the name of the mysterious 'view that cannot be found' and fields with bad formulas

On a web page with tons of fields (I have some with hundreds), it’s pretty darned hard to figure out which field is not working because of a bad value in it (ie text where a number should be). Why not pass along the offending viewname, or even better, the field that’s blowing up? It would be massively helpful, is it that hard to code into Notes’ error messages?Sometimes you get get the field name if you open the doc in a Notes client, but not always.

Subject: While I’m griping, how about providing the name of the mysterious ‘view that cannot be found’ and fields with bad formulas

Agreed, having same problem. I have a db that works perfectly on one server, on its production box you can’t open any forms without getting the dreaded “a view of that name” error. Mine is occuring in the comboboxes. The formulas work on my development server, but not on production. ACL is identical - go figure.