It is such a simple script, I would recommend recreating the script from scratch. Don't reuse the script. Don't copy & paste.
Furthermore, I highly recommend that you start by turning error capture on.
go to layout
test for an error in case you didn't land on the desired layout.
The Delete All Records is too dangerous to ever ASSUME you are on the correct layout.
If you set the script to run with full access privileges, do you still get the error ?
Does your "Order Edit" have any script triggers? Maybe a script that is being triggered has an incompatible script step.
Alright! Recreating from scratch did the trick.
Also...good idea about error capture to check the correct layout. thanks.
Appreciate everyone's help.
My two cents: do not check being in the correct layout, check being in the intended table. Something like:
Get ( LayoutTableName ) = Left ( GetFieldName ( yourTable::anyField ) ; Position ( GetFieldName ( yourTable::anyField ) ; "::" ; 1 ; 1 ) - 1 )
makes sense. thanks much.
You said you did extensive work in the table. Could you have deleted a field that is on the layout and this is causing the error?
Since you are using this layout for deletion, perhaps creating a special layout just for deletion, Delete All Records Layout, and only have one field on it such as the ID Number field.
If you are using a layout with all fields, then perhaps a calculated field is causing the error. So, don't use all fields, just one.
Looks like the script was corrupted somehow. I rebuilt it from scratch and it worked fine. But you may have a good point for deletion purposes.
Maybe not the Correct Answer
If you Delete All, with no Records Found, you will get Error 3 ( Command Not Available )
When you run script on server, you must first set the conditions you might see on Client, e.g. that you have a found set, and that any Globals are set
My guess is your Default Found Set somehow got changed. Adding a "Show All Records" would help greatly
> I have a script that runs on a schedule on my FM Server 13. Runs every night and has been in place for at least a couple weeks now with no problem. Starting today, the script won't run, resulting in error (3)