I would suggest that firstly pausing a script in Find Mode is fraught - don't do it. I suggest that you ask your user for their input in a Custom Dialog Box, setting a field in the table for their input, check it for consistency, then use this as your find field and sort field
I would suggest to not let the user going to Table View.And it is simple to let him going to a layout wich has only that field.
Make the script like this
set variable[$findvalue = usercondition on which it will perform the find]
go to layout[blank layout having the search fileds only]
enter find mode[daon't pause]
go to required layout
Sort Records by Field
View As [View as List]
The problem with your original script, BTW, is that it enters find mode, but never performs the find. Had you included a perform find step, it would have worked, but I agree that entering find mode and pausing for the user to input criteria is not the best, most user friendly option. I also find table view to be a frequent source of tech support calls that I could do without as it gives the user too much freedom to re-arrange the view and then they call me when they get into trouble. I prefer a list view layout where I can keep the user from getting into that kind of trouble.
Here's a basic outline of a scripted find I use. It's nearly identical to the one recommended by Atauf:
Enter Find Mode  ---> clear the pause check box
Set Field [Yourtable::YourField ; Globals::GlobalFieldWithCriteriaEnteredByTheUser]
Set Error Capture [on] ---> keeps error dialog from interrrupting your script if no records are found.
#Then sort your records etc as needed to present your found set of records the way you want your user to see them.
Then all you need to do is place that field with global storage on a layout somewhere so that the user enters criteria into that global field, then clicks a button to perform this script. There are many possible variations of this basic approach.