I know this conversation took place some time ago, but anyway...
I added another form to my db and called it GeneralError. On the form
$$ReturnGeneralError i put a meta refresh tag in the HTML head, and made the
refresh URL point to the new GeneralError form.
Parts in brackets are of course substituted with fields on the
$$ReturnGeneralError form.
This will give me an automated redirect to the GeneralError form, which does
not have the same limitations as the $$ReturnGeneralError form. I just put the
needed fields on the $$ReturnGeneralError and GeneralError forms. Massage the
Query_String_Decoded into fields corresponding to the parameters in the
GeneralError form, and have it all taken care of by a WebQueryOpen agent that
can do anything I want.
To be on the safe side I also put a link on the $$ReturnGeneralError form in
case the web user is not redirected automatically.
I know this conversation took place some time ago, but anyway...
I added another form to my db and called it GeneralError. On the form $$ReturnGeneralError i put a meta refresh tag in the HTML head, and made the refresh URL point to the new GeneralError form.
<meta http-equiv="refresh" content="0; url=http://servername/directory/database.nsf/GeneralError?ReadForm&URL=[Path_Inf o]&Ref=[HTTP_Referer]&Msg=[MessageString]">
Parts in brackets are of course substituted with fields on the $$ReturnGeneralError form.
This will give me an automated redirect to the GeneralError form, which does not have the same limitations as the $$ReturnGeneralError form. I just put the needed fields on the $$ReturnGeneralError and GeneralError forms. Massage the Query_String_Decoded into fields corresponding to the parameters in the GeneralError form, and have it all taken care of by a WebQueryOpen agent that can do anything I want.
To be on the safe side I also put a link on the $$ReturnGeneralError form in case the web user is not redirected automatically.
/Peter http://thor.pyttemjuk.nu/