I appreciate all your time you're spending on this. I'll do some testing on another machine tonight. I'll update tomorrow.
I appreciate all your time you're spending on this. I'll do some testing on another machine tonight. I'll update tomorrow.
Too bizarre! Running in Access 2010 the message pops up. Debug takes me to the Combo2 GotFocus event every time. So I modified with:Unfortunately, it still hits the Combo2 GotFocus event and the message pops up but at least it will set focus. The mystery is why does it hit the Combo2 after about 4 back & forth on the tabs? And why in 2010?Code:If IsNull(Me.Text7) Then Me.Text7.SetFocus ElseIf IsNull(Me.Text9) Then MsgBox "Please enter a PCL Title" Me.Text9.SetFocus End If
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
I guess I'm pleased that you were able to duplicate the problem. I installed on the client's machine, and the problem occurred. I was beginning to wonder if maybe it was because of the linked tables. But since you duplicated, that is ruled out.
If the mystery can't be solved, the only thing I can suggest is to eliminate the MsgBox line.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
It sounds like you haven't responded to the message. If you respond, it then displays the message "Please enter a Print Run ID." Then a run time error message.
I do respond to the messages. Without my code revision I get the runtime error.
Just tested again and noticed that sometimes clicking tab 2 (Edit Print Run Edit Info) focus goes to Text67.
I have never seen this with earlier versions. More reason not to upgrade to 2010. I have not been impressed with 2010.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
So Access 2010 could be the culprit. At least I know that since you've reviewed the DB, the problem is not due to coding. My solution is to add your code listed above. It prevents the focus from being in the wrong location. Thanks for all your time spent on this thread.
Last edited by crowegreg; 08-27-2011 at 05:15 PM.