Unfortunately I don't think anyone can help you with this without knowing much more information. Any help will only be a guess.
What do you mean by "alerts popping up"? Are you referring to dialog boxes? Is it something set up in your FileMaker Pro database to tell the user something? or is it a FileMaker error? How do these alerts appear to the user? In a window? In a dialog? It does not sound like standard FileMaker Pro behaviour!
Sorry, sometimes explaining these problems is more complicated than they first appear, especially when you don't know the correct terminology!
It is Filemaker Pro 9.
It's not an error, it's a window in which are a list of 'To Do' alerts, i.e. Prepare for meeting, call this person at this time or don't forget to… .
So, regardless of when the To Do was created for or snoozed until, when they start to type elsewhere in the database a dialogue box appears that says, "Before typing, press Tab or click in a field, or choose the New Record menu command." with an 'OK' button.
Once you've clicked 'OK' you can continue typing which is fine if you don't touch-type and have to watch what you doing. If you touch-type, you could be typing away and think you've finished your insertion only to find that the problem has happened again and you only managed to input the first four words or so before the "Before typing, press tab…" dialogue box appeared.
I hope that is enough info?
Thanks for your quick response.
OK, that is much better information to work on.
What appears to be happening is that the user or the database is committing the record. When that happens and the cursor is not in a field, FileMaker Pro displays the 'error' dialog you are getting. This is not normal behaviour.
Question: does the record get committed if you do not type anything for a minute? If not, can you type slowly and try to identify when it commits?
It is a difficult thing to troubleshoot without a copy of the database. It seems to be something set up in the database itself.
Could you explain what you mean by 'committed'?
When you type data into a field on a layout, that data is not 'committed' to the database until one of certain actions occur. These actions include things like pressing the Enter key, creating a new record, switching modes or clicking on an area of the layout outside a field. When the record is committed, the cursor is not in any field. If you start typing in that circumstance, FileMaker Pro will alert you that you either need to click in a field or create a new record before typing.
Does that explain it?
I have shown these threads to the person who alerted me to the problem and they aren't convinced we are addressing the problem so, I have added a link to the screen grab from their PC.
Maybe having a visual aid will help.
The screen shot says "Before typing, press Tab or click in a field, or choose the New Record menu command". This means you do not have any field selected. When you start to type, FileMaker doesn't know what field you want this information to go into. Therefore, either press Tab (to enter the first field), or click into a field (to make it active) or choose the New Record menu command which will put you in the first field of a new record, and you can start typing.
Normal behaviour: An edit field is "focused", text insertion caret inside the text field is blinking or some text inside the field is selected. User can type into the text field (no alert dialog).
Normal behaviour: No edit field is "focused", no text insertion caret and no text inside any field is selected. When user attempts to type, alert dialog pops up to inform that an edit field must be "entered" first (and hints at ways the user can do that e.g. click in the field first or tab to it).
Abnormal behaviour: An edit field is "focused", etc. When user attempts to type, alert dialog pops up as if no edit field had been "entered" (by clicking in it first, or tabbing to it, or etc.).
For clarification, does that last one describe the problem being discussed?
Just to add to the already great help you're getting:
Assuming that the error is coming up at the appropriate time (when no field is in focus), I would assume that your users are having this problem directly after performing some script (one that creates a new record, that brings them to an edit layout, etc.).
To solve the problem, go back to this script and add one more script step:
That will give you the behavior it sounds like you're desiring.
I tried to post a reply yesterday but it doesn't seem to have worked.
Thanks for all your help.
This is getting very confusing with all the jargon.
But we seem to be experiencing what TheGSO said:
"Abnormal behaviour: An edit field is "focused", etc. When user attempts to type, alert dialog pops up as if no edit field had been "entered" (by clicking in it first, or tabbing to it, or etc.)."
So hopefully that helps.
Thanks for the suggestion jsalzer but unfortunately I can't use the script because I didn't write the database and wouldn't have a clue what to do.
Is there now a simple Filemaker solution to the problem or is it a database issue?
Just to clarify. When TheGSO says "in focus", what he means is that the cursor is in the field and actively blinking, as if ready to receive text.
Do you actually see a cursor in the field you want to type in when you get this message?
Hi, Jsalzer and everyone,
Thanks for al you help and patience.
Yes, there is a blinking cursor and the user could have already typed a few words and then, suddenly, the dialogue box telling the user to "Before typing, press tab…" appears.