I am having a problem that I wonder if someone can explain/help to solve. The description is as follows:
Ebase version: 2.20 7/14/2007 Release build
Type of install: Server/Client multiuser
Full text of this item is available to ebase community members only.
Please log in or click
here for membership information.
New problem, or came with your upgrade?
Hi GRuB -
This bug wasn't apparent when 2.20 was released, so I wonder if it didn't crop up after you installed... perhaps it's unique to your ebase, the result of damage incurred in a computer crash. Sounds like you have a broken script reference: one script has lost its "pointer" to a script it needs to call upon to complete its task. Easy to fix, once you can find the broken reference.
If the problem is in the 2.20 distribution, someone here at ebase will need to fix it, and then we can tell you where the fix is. If it's your own crash damage, any FileMaker consultant can help you track it down. (It's a lot easier with the Script Debugger, a tool that comes with FileMaker Developer.) Once you know where the missing script reference is, you can look in a clean copy of the 2.20 distribution to learn what _should_ be there.
Cheers,
Allen
allen@cdsnw.com
Problem came with upgrade
Thanks for the reply. The problem arose after the upgrade. I can't tell if it is local or in the ebase version, but would think it's local. There has been crashes in the past.
I will start looking for the broken script.