How do I suppress error code 307? (Set Error Capture does not work for this error code)
I would properly document it and report it as a bug.
If it can be verified as designed in functionality then this KBA should be updated.
Set Error Capture does not suppress alert dialogs with some scripts | FileMaker
Thanks and where do you report a bug?
Report a Product Issue
The real issue however is to scrutinize your deployment as why the error happens. It is not a trivial error and a fairly critical one.
Yes I agree. We use FM 13 and FM 14 and the same script on FM14 does not pop up the error but with FM 13 it does since the new Server update got released 18.104.22.1682 , thats why I'm looking for a work around.
I had the exact same issue Steven, updating FM13 to FM14 Server, with FM13 clients. I got the "307" error just trying to use a drop down calendar to change a date. I just updated that client to FM14 Pro and the "307" error went away. I haven't found any other workaround, but the update to FM14 took care of it.
Thank you for your post.
The 307 error will show up with any version of FileMaker Pro prior to 14.0.4. Our Development and Testing department has discovered this occurs when modifying a field on a form in Form view that contains a sorted portal that shows either 0 or 1 row of related data. A workaround is to go to another record and then back again.
I have attached this thread to the original report. When more information becomes available, I will post again.
To address Steven's original point, it looks like this error is distinct from the normal Filemaker error (hence the "Unknown Error" bit). It seems to be a lower-level error that the client throws that is unrelated to (or at least doesn't have the same behavior as) the normal 307 error.
My guess is that this error would show up as a -1 ("Unknown Error") for trapping purposes, but I haven't tested it.
We have this error with FileMaker Server 14 (running on El Capitan - but we didn´t install FMS14 on any other OS, so it may be OS independend):
FM14.0.4 Clients can Log into our solution without problems.
FM13 an FM13 Advanced not. (Unkown Error 37, no crash, but a certain layout is opened, that is only opened, when certain values are not pressent - the Layout for entering the license code of our solution)
Solution for us:
The error appears right at the start of the first file, when te startup script is executed. We didn't investigate, at which steps exactly the error occurs, as it is sufficent for us to set a script pause of 0.5 seconds right at the beginning.
If memory serves me right, I read somewhere else here in the forum, that a script pause will also help fmgo14 when it crashes. So I think: When all of us have databases, that work well under FMP13 and FMS13, but some constellations NOT (FMP13/FMS14 = problems, fmgo14/fms14 = problems, but FM14/FMS14 = works), than there is a problem with FMS14
Thanks for the info, but did not handle the issue, error 307 still shows up.
I'm also experiencing the 307 error, however in my case there is no "sorted portal that shows either 0 or 1 row of related data".
This is with a FileMaker Pro 12.0v4 client accessing a file peer to peer hosted by a FileMaker Pro 14.0.4 machine.
At what point does the error 307 occur? What actions are you taking when this occurs?
If you go to another record and back again, does the error still occur?
It was part of the startup script - I was trying to set a text field with a value. This was in a single record table so there is no other record to go to unfortunately.
Thank you for the information.
For testing purposes, try going to another layout and then back again. Does this still produce the error?
What other objects do you have on the initial layout?
Hi TSGal - there's no objects on this layout apart from some buttons and merge fields/labels (it's a home screen). Changing layouts doesn't appear to make a difference - it's when the startup script runs it navigates to this layout and attempts to set a field, so the user has no control over the scripted process.
Our Development and Testing departments would like to see a copy of your solution to understand why the 307 error is being generated. I have sent you a private message with instructions where to send the file.
I have received your file. Thank you.
The file has been sent to Development and Testing for review. I will let you know when I hear something.
Are there any updates on this issue? I recent ran into almost the same issue where error 307 presented during "Set Field" step.
Client: FileMaker 13
Host: FileMaker Server 14
There is no update at this time. I have also attached your post to the original report. When more information becomes available, I will post again.
Same Error 307 problem, BUT I DID MANAGE A FIX.
I have upgraded a solution from v11 to v14 and this Error 307 is the only bump in the entire upgrade. Currently using Mac FMPv13.0v3 with Mac FMS v22.214.171.124
I am seeing this on a field in a header body part. The field is a related field in a straightforward Cartesian relationship. Originally, the field displayed a popup menu that stored a 1 or 2 and displayed valuelist label corresponding from a related table. I disabled ALL of that and made it a straight field where I manually typed 1 or 2 and I still received the error.
My fix was to turn off indexing for that field. I changed the value and no error. I turned indexing back on to enable using the relationship and it works without issue, still. So, try turning off indexing for which ever field gives that error and turn it back on.
Thank you for the information. I have sent this information to Development and Testing for review.
This issue does not occur with FileMaker Pro 15 clients.
14.0.6 addresses the issue (as well as 15.0.1)
This solution worked for me on a local computer logging solution file...
Turned off all indexing on fields I was trying to set, and the script which was failing worked..
Retrieving data ...