Why do you have Go to Object? try to disable that step or verify that the name of the object is correct.
Set Field does not even need to have the fields on the layouts as long as they are in the relationship paths.
This is a password collection database that we are using to replace an old Lotus Notes database.
So everything is hidden and only are showing upon typing passwords.
Name is correct. :/ checked..
There is some global check fields that am using for authentication on that panel that am trying to open, that i need to reset the value in. (for other scripts and show / hide fields).
Go to Layout, is only there becouse am using the same script for several functions
Go to Object, is the main thing with the script.. its for swapping showing portal.
Active Panel field is for knowing the last panel upton swaping.
Check 1 and 2: are fields for knowing if correct password is set or not. reason why am using that i notised that it didnt reset both otherwise.. and it works =) might not be the prittyest but it does what its suppuse to..
exept going to that object. :/
When you run the debugger, which step does it error out at? The Go to Object step?
Is the Line 3 a related Table Occurrence? That could be the error. What error does debugger give you?
I dont have advanced version of Filemaker. :/ only the Pro one..
I do have an old license for FM 8 with advanced laying around.. but not installed. since all our other clients are version 15. :/
So i cant really answer you on that , sorry
Can it be so easy that having several scripts with same code (the 3 lines).
so the stacking of the show/hide makes it not work ? is that possible..? just a theory.. =D
1 of 1 people found this helpful
I usually put these kinds of lines right after Go to Layout and then I Refresh window after the steps:
Go to Layout ...
Show/Hide Menubar (Hide)
Show/Hide Toolbars (Hide)
Show/Hide Text Ruler (Hide)
Refresh Window ...
Go to Object ...
moved the lines and added refresh window..
and its working.. =D
But thats really strange... :/