jasonbernett Report post Posted 01/08/2009 06:29 PM What is wrong with this? I am always getting the failed path. Also, is there an easy way to debug VB script in VG (check for syntax, errors, result codes... etc)? set vg = CreateObject("vgServices.CommandLink") i = val("$RV_ENTEREDNUMBER") if i < 11 then sResult = "verify_passed" else sResult = "verify_failed" end if vg.Run_ResultReturn $RV_LINEID, sResult set vg = Nothing Share this post Link to post
SupportTeam Report post Posted 01/08/2009 08:14 PM Please post the vgEngine trace capturing the call, we can then see what happened. Share this post Link to post
jasonbernett Report post Posted 01/08/2009 08:27 PM Here are the logs. Log_Files.zip Share this post Link to post
jasonbernett Report post Posted 01/08/2009 08:40 PM For good measure here is the script. I have it starting in Q1A. survey7212.vgs Share this post Link to post
SupportTeam Report post Posted 01/09/2009 03:48 AM Try just double-clicking the VBScript file created by VoiceGuide. If there are errors in it then you will see a message box. The script is at: C:\Program Files\VoiceGuide\temp\vbs_1_1.vbs - but check the vgEngine trace for name of script file if you dial in on a different line or change the script. These vgEngine trace lines tell you which script file is the right one: 132550.484 6 1 copy of verification script ran: vbs_1_1.vbs ... 132550.484 6 1 RunVBScriptFile [wscript][C:\Program Files\VoiceGuide\temp\vbs_1_1.vbs][] timeout=0 (vbsPath=C:\Program Files\VoiceGuide\temp), start (new Process) I'd try changing line: i = val("$RV_ENTEREDNUMBER") to: i = $RV_ENTEREDNUMBER Share this post Link to post
jasonbernett Report post Posted 01/09/2009 04:04 PM That fixed the vbs script... Thanks much! Share this post Link to post