kenseye Posted November 21, 2001 Posted November 21, 2001 After updating my solution, I get a "cannot find script or script has been deleted" error, but still carries out script. I reformatted the button to play script, redid the script with same error. Only set error capture on elliminated the message. Any ideas as to why I was getting the error? script read: Copy(Select, Record#) Perform Script(subscripts, Add Payment)
pspafford Posted November 22, 2001 Posted November 22, 2001 Hey kens. Check your Add Payment script to see if any of the Perform Script steps don't specify a script. Then, check those scripts for the same thing. Paul
Steven H. Blackwell Posted November 22, 2001 Posted November 22, 2001 If you set error capture ON, be sure to capture the error and handle it. Otherwise items can fail with no warning. HTH Old Advance Man
kenseye Posted November 23, 2001 Author Posted November 23, 2001 I cannot seem to find any script error... I even tried re-doing all the scripts and external scripts and still same error. With set error capture on, all runs ok...how do I capture the error if there is one?
The Bridge Posted November 24, 2001 Posted November 24, 2001 quote: Originally posted by kens: I cannot seem to find any script error... I even tried re-doing all the scripts and external scripts and still same error. With set error capture on, all runs ok...how do I capture the error if there is one? In a situation like this, I liberally sprinkle Show Message steps in my script with a brief description of what I expect the script to do next. It may help you pinpoint where your script is breaking. As for error capturing, the Status(CurrentError) function returns the error code for the most recent script step only. I tend to enclose Script Steps most likely to cause errors (e.g. Find, Print, etc.) with Set ErrorCapture, and within that I have a conditional statement (e.g. If Status(CurrentError)<>0) to handle any errors.
Steven H. Blackwell Posted November 24, 2001 Posted November 24, 2001 quote: Originally posted by The Bridge: In a situation like this, I liberally sprinkle Show Message steps in my script with a brief description of what I expect the script to do next. It may help you pinpoint where your script is breaking. As for error capturing, the Status(CurrentError) function returns the error code for the most recent script step only. I tend to enclose Script Steps most likely to cause errors (e.g. Find, Print, etc.) with Set ErrorCapture, and within that I have a conditional statement (e.g. If Status(CurrentError)<>0) to handle any errors. There are specific errors, and there is a list of soem of them in the on-line Help. To capture the exact error, create a global field of the type number. Immediately after the event that might cause the error, Use a Set Field into that global with Status(CurrentError). This does not apply to ODBC. ODBC has its own error step. HTH Old Advance Man
kenseye Posted November 24, 2001 Author Posted November 24, 2001 Thanks for your help....I found the error in a subscript.
Recommended Posts
This topic is 8404 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now