Jump to content

script error after updating solution


This topic is 7270 days old. Please don't post here. Open a new topic instead.

Recommended Posts

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)

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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

Link to comment
Share on other sites

This topic is 7270 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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.