FileMaker 3.0v5 script error: solved!

Regarding the script errors in FileMaker 3.0v5, as reported here previously: Thomas Hesser (the user who reported the problem) and FileMaker tech support worked together to find a solution:

The results of our discussion were that the problems with our database were covered under the Read Me and documentation found on the FileMaker web site. While the documentation apparently covers the changes, if you have complicated scripts, the effects of the changes may not be obvious until you start dissecting the script. In our particular case, one of the scripts was doing a search for records with empty date fields (using "="). The changes in the updater no longer allow this action to take place (apparently many of the changes are constrictions on certain actions). So, what was happening is that when that script was being run, it hit that "search for empty field" part of the script and just hung up the database (i.e., the script stopped running and dropped you into an unusable screen).

A personal note: FileMaker has to be one of the best companies we have worked with in responding to bug reports here at MacFixIt. They invariably and quickly track down the cause of every problem reported, and reliably get back to us with a solution or explanation.