Can confirm this bug on FMPA 10v3, OS X 10.6.2
Edit added: However, if you delete the field in Manage Database, you obtain a warning that the field is used in Script "xy".
Hi Martin, thank you for confirming - much appreciated! :smileyhappy:
I know we'd get a warning if the field was deleted but the field might be corrupted and would be 'missing' as well - that's how I discovered it originally several months ago. I've been studying error codes in corruption, as well as missing tables when on other servers etc.
And I know we can proceed and get other errors (check the link I provided). But can we guarantee in all instances that we won't ever need to know that field is missing or broken while in find mode before the Perform Find? Example - if we are using that field to duplicate the find request (which contains that broken field) and then we modify the request with additional information, we don't get 508 but rather 400 (missing find criteria), which is not normally considered dangerous and is usually addressed with Custom Dialog to User and chance to try again.
I dislike uncertainties, particularly when it should produce the error and does in Browse. It is difficult to find out which errors are thrown and when; they tend to overlap and offset each other at times. We need to trust that we at least GET an error when we should; not later on in the script.
Has this at least been passed on to the Development and Software Quality Assurance (Testing) departments so there is possibility of it being fixed?
Thank you for your post.
Yes, this has previously been reported. I have added your information to the original case for our Development and Software Quality Assurance (Testing) departments to review.