Why do I get an error in a Text Box's "On Enter" event in an "empty" Access Form?
I am developing an Access 2007 "project" (ADP) as a front-end to a SQL Server 2005 Express database.
I have a "continuous" Access Form that lists the records in a Table before they are printed on an Invoice or Credit Note. These rows of data can be modified or new rows added within the Form.
In the Footer of the Form I have a large Tab Control with several Tab Pages. Each of these Tab Pages contains further Combo controls and Text Box controls that govern what will be printed on the Invoice or Credit Note when it is eventually printed.
Normally this Form displays rows of records in the Detail Section when it is first opened, and I have no problems as I move from Tab Page to Tab Page in the Footer. However, if there are no records displayed to begin with, I get the following run-time error when I open a Tab Page and the focus is placed on a Text Box in the page.
Run-time error 2185
You can't reference a property or method for a control unless the control has the focus.
This happens in Text Boxes that contain messages that might be printed on the Invoice or Credit. It happens in the "On Enter" event procedure where I set ".SelStart" and ".SelLength" to 0, to position the text cursor at the first character of the text rather than selecting all the text.
I do not get this error if the Tab Page's first control is a Combo Box or if it is a Text Box for which I have not established an "On Enter" sub procedure. The cursor seems to sit in these controls OK. If I add a row of data to the Form's Detail section before opening the Tab Pages that have the "On Enter" procedures I do not get the error message.
Can someone explain to me why I get this error message when my Form is empty? I have another text control called ".txtLineCount" that I use to display the number of data lines. Even when I add the expression :
"If Nz(Me.TxtLineCount, 0) > 0 then" in my "On Enter" event procedure I get the error message at that point.
Many thanks. Colin.
I have a "continuous" Access Form that lists the records in a Table before they are printed on an Invoice or Credit Note. These rows of data can be modified or new rows added within the Form.
In the Footer of the Form I have a large Tab Control with several Tab Pages. Each of these Tab Pages contains further Combo controls and Text Box controls that govern what will be printed on the Invoice or Credit Note when it is eventually printed.
Normally this Form displays rows of records in the Detail Section when it is first opened, and I have no problems as I move from Tab Page to Tab Page in the Footer. However, if there are no records displayed to begin with, I get the following run-time error when I open a Tab Page and the focus is placed on a Text Box in the page.
Run-time error 2185
You can't reference a property or method for a control unless the control has the focus.
This happens in Text Boxes that contain messages that might be printed on the Invoice or Credit. It happens in the "On Enter" event procedure where I set ".SelStart" and ".SelLength" to 0, to position the text cursor at the first character of the text rather than selecting all the text.
I do not get this error if the Tab Page's first control is a Combo Box or if it is a Text Box for which I have not established an "On Enter" sub procedure. The cursor seems to sit in these controls OK. If I add a row of data to the Form's Detail section before opening the Tab Pages that have the "On Enter" procedures I do not get the error message.
Can someone explain to me why I get this error message when my Form is empty? I have another text control called ".txtLineCount" that I use to display the number of data lines. Even when I add the expression :
"If Nz(Me.TxtLineCount, 0) > 0 then" in my "On Enter" event procedure I get the error message at that point.
Many thanks. Colin.
jmro20
Try setting the focus in the first line of the function like this: [YourTextBox].SetFocus
ASKER
Thanks for the prompt response, jmro20.
I tried your suggestion (with the lines shown below) but am still getting the same error message.
Me.txtTranTermsMessage.Set
With Me.txtTranTermsMessage
.SelStart = 0
.SelLength = 0
End With
The VBA appears to crash on the ".SelStart=0" line. So it seems to be happy with the "Me.txtTranTermsMessage.Se
I think it is to do with having no real records in the continuous Form. I could live with that if I had a way of recognising that fact. My own ".txtLinesCount" field generates the same error when I try to check it when the Form's recordset is empty.
Can anyone tell me a safe way of checking for an empty recordset?
Regards. Colin.
I tried your suggestion (with the lines shown below) but am still getting the same error message.
Me.txtTranTermsMessage.Set
With Me.txtTranTermsMessage
.SelStart = 0
.SelLength = 0
End With
The VBA appears to crash on the ".SelStart=0" line. So it seems to be happy with the "Me.txtTranTermsMessage.Se
I think it is to do with having no real records in the continuous Form. I could live with that if I had a way of recognising that fact. My own ".txtLinesCount" field generates the same error when I try to check it when the Form's recordset is empty.
Can anyone tell me a safe way of checking for an empty recordset?
Regards. Colin.
Try this:
If Len(Trim$(Me.txtTranTermsM
Me.txtTranTermsMessage.Set
With Me.txtTranTermsMessage
.SelStart = 0
.SelLength = 0
End With
End If
If Len(Trim$(Me.txtTranTermsM
Me.txtTranTermsMessage.Set
With Me.txtTranTermsMessage
.SelStart = 0
.SelLength = 0
End With
End If
ASKER
As I typed my previous message, it occured to me to try the following, in place of the ".SetFocus" expression before I set the ".SelStart" and ".SelLength" values :
"If Me.Recordset.RecordCount > 0 Then"
This seems to work OK. At least I don't get the run-time error when I have no records listed in the Detail section of my Continuous Form.
Does anyone have any further suggestions or thoughts they can offer on how better to handle this?
Thanks. Colin.
"If Me.Recordset.RecordCount > 0 Then"
This seems to work OK. At least I don't get the run-time error when I have no records listed in the Detail section of my Continuous Form.
Does anyone have any further suggestions or thoughts they can offer on how better to handle this?
Thanks. Colin.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes the problem is with the empty recordset.
ASKER
Is it OK to accept my own response as the answer? I think we proved that the empty recordset causes the problems when we try to modify a control's properties.