VGR iform error when running in verbose mode

[SK]

Has anyone encountered this error when running a VGR iform in verbose mode?  It only occurs in one particular form.  I do not see anything obvious in the HTML or VGR script that would cause the issue. I checked the server log and rtable-A.log does not show any errors.  

   

No data returned from the server.

Check the server logs for detailed information.

This could be from an invalid TTY id or an invalid patient id.

[Scott Morris]

That's new to me; are you terminating your VGR the same way as the others?  Maybe you could put in a DISPLAY screen before you exit to show your orderstring to see if there's anything suspicious in there?  If you figure it out, I'd love to hear what it was.

[SK]

The error is displayed immediately - the HTML does not get a chance to display.

[Scott Morris]

Wow, that's interesting. Then I'd say we need to think about what's happening in your INIT phase for this particular iForm.  Are you doing active order awareness? Are you pulling any variables via INIT,MAP (vs INIT,SET)?

[SK]

Sorry I am not familiar with active order awareness.  I am not pulling in any variables via INIT MAP.

[Scott Morris]

And, just to confirm, you're saying that it doesn't give an error unless you open it in verbose mode?  If that's the case, it likely has something to do with one of your VGR variables (since, when in verbose mode, it generates a table at the bottom of the page with debug information including the contents of all of your variables).

I'd be willing to take a quick look at it if you want to email it to me. (scott (dot) r (dot) morris (at) gmail (dot) com)

[SK]

I removed many old unused fields from the VGR script that were no longer on the HTML page and resolved several  instances where the same name or  field ID was used for two different fields.  I also reviewed the HTML code and removed/cleaned up all the extraneous html  statements added by a code generator.  The script now runs in verbose mode.  Lesson learned.  The tip about looking at the INIT phase code when verbose mode doesn't start immediately put me on the right track.  Thanks for the help.