TomStorey Report post Posted 01/18/2008 02:38 PM We do a lot with VBScript. It is easy to miss something when writing new programs. Using VG V7, no error message boxs show so there is no way to know where the programing error may be in the script. If there is one little mistake the whole script fails, times out and jumps to the timeout path. What can we do to get error messages from VBScript programs. This is becoming a big problem. We have one development box for a number of programmers that working on different programs at different times. Trying to go back through a large program looking for a problem that you have no idea where it may be is bring new program to a stop. I know you said this problem is because VG runs as a service now and this may be a pro, but not having error message boxes is a big con. There needs to be made someway of getting these error messages during development time. Run time can maybe be handled, but development time is when we need to be able to find the problems. Share this post Link to post
SupportTeam Report post Posted 01/18/2008 10:34 PM The best approach to debug systems which are unable to display messages on the screen is to use tracing from within the script which are then logged in the vgEngine log files. Please see: http://www.voiceguide.com/vghelp/source/ht...tracelogadd.htm This will let you track scripts progress and if there is an problem with the VBScript which results in it's termination then you can narrow down the error to a particular line using this approach. Share this post Link to post
