I have been working on inview editable view and have a length of code written in it. As I try to enhance the code, I do write erroneous code and try to resolve it using the debugger. In inview edit event, I am not able to debug the script that I have written as it keeps jumping from one event to another (Query Req, Validate Req, Save Req) and hence I have to debug using msgboxes line after line and see which line is giving me the error.
Is there a better way to debug without making the code messy?
is that this is an event that’s heavily involved in focus changes. If you’re not debugging and you start to edit a field in the view, then switch to another window, that means you’re done editing that field. But when you debug, the debugger window is another window, so during you’re debugging you’re making focus changes that you wouldn’t make if you ran it without debugging. So it doesn’t work the same way.
You might try using the status bar instead of msgbox; that would be less intrusive. Or you could write data to a log file and close the file after each line (to flush the output buffer) and have a process running in another window to poll the file every second and display any changes.
Thanks Andre. Printing to status bar is a good option. But it will still make the code look messy with the print statements, and if that is how inview edit works and I guess we don’t have much options.
