Ms Access 2007 Error 2185
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the you cannot reference a property or method for a control unless the control has the focus workings and policies of this site About Us Learn more about Stack
Runtime Error 424
Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Run time error 2185 up vote 2 down vote favorite I getting a run time error 2185, "You can't reference a property or method for a control unless the control has the focus ...". This is my code that I am using. Private Sub Command5_Click() Dim cardno As Integer cardno = cardnumber.Text DoCmd.OpenForm "search_card_number", acNormal, , WHERE & cardno = [Account Number] End Sub ms-access access-vba share|improve this question edited Dec 20 '13 at 16:30 HansUp 79.3k114371 asked Dec 20 '13 at 12:17 Steve 481211 add a comment| 3 Answers 3 active oldest votes up vote 3 down vote Referencing the .Text property of a control requires it to have focus. Simply drop that and it should work (the default is .Value) OR Try putting in the SetFocus method as advised by Access, i.e. Private Sub Command5_Click() Dim cardno As Integer cardnumber.SetFocus <-------Use this line to set the focus cardno = cardnumber.Text DoCmd.OpenForm "search_card_number", acNormal, , WHERE & cardno = [Account Number] End Sub share|improve this answer answered Dec 20 '13 at 12:35 sonams 1,20741435 I get a runtime error 6, overflow. but the carnumber.text did get the value I was enter in textbox –Steve Dec 20 '13 at 12:42 I guess data can no longer be held by an integer. Try changing the line Dim cardno As Integer to Dim cardn
+ Ask a Question Need help? Post your question and get tips & solutions from a community of 418,595 IT Pros & Developers. It's quick & easy. Run-time error '2185' You can't reference a property or method P: 77 Sep410 Hi all, Here is my code: Expand|Select|Wrap|Line Numbers PrivateSubCommand12_Click() DimstrSqlAsString strSql="Deletefromtbl_citywhereCityId="&Val(Me!txtEmail.Text)&";" Setcn=CurrentProject.Connection cn.ExecutestrSql Debug.Print"MyTableViewcreated" Setcn=Nothing EndSub I get the Run-time error '2185' when I run it. You can't reference a property or method for a control unless the control has the http://stackoverflow.com/questions/20703479/run-time-error-2185 focus .!!!!!!! If I put this line after defending of the strsql everything work well but I don't want to have this line in my code. Expand|Select|Wrap|Line Numbers 'Me!txtEmail.SetFocus There are some SQL statements which has 2 conditions I can't set the focus for both of them at the same time. Oct 7 '08 #1 Post Reply Share this Question 5 Replies https://bytes.com/topic/access/answers/844004-run-time-error-2185-you-cant-reference-property-method Expert 2.5K+ P: 3,532 missinglinq In Access VBA the Text property is only available when the control has focus, as you've seen .The Text property is seldom used in VBA. Use the .Value Property instead. It doesn't require focus to work. And since it's the Default Property for a textbox/combobox, you don't actually have to include it! txtEmail is the same as txtEmail.Value Linq ;0)> Oct 7 '08 #2 reply P: 77 Sep410 Thank you.It is working now. Oct 7 '08 #3 reply Expert 2.5K+ P: 3,532 missinglinq Glad you got it working! Linq ;0)> Oct 7 '08 #4 reply P: 9 sirdevo I had a couple of textboxes I needed to change the .text property on, but when I would setfocus to update the textbox it would cause problems by activating all my events I had placed on those textboxes. It allows me to change the values without causing events to trigger. Sir Devo Nov 12 '09 #5 reply Expert 2.5K+ P: 3,532 missinglinq As I said previously, there is seldom any reason to use the Text Property in Access VBA,
Search Community Links Social Groups Pictures & Albums Members List Calendar Search Forums Show Threads Show Posts Tag Search Advanced Search Find All Thanked Posts Go to http://www.access-programmers.co.uk/forums/showthread.php?t=233659 Page... Thread Tools Rate Thread Display Modes 09-19-2012, 08:48 AM #1 redbe4rd Newly Registered User Join Date: Sep 2012 Posts: 12 Thanks: 2 Thanked 0 Times in 0 Posts http://www.pcreview.co.uk/threads/selstart-error-run-time-2185.3308525/ Runtime Error '2185' when filter returns no results I've searched through the forums for posts regarding Error '2185' (You can't reference a property or method for a control unless the control has ms access the focus.), but can't find anything so far that has helped my situation. Situation: I'm creating an item look-up form with 2 criteria that I wan't to auto-filter as the user types. I'm placing my code in the Change event of the textbox, and only calling the .text for the current textbox (.value or no property at all for the other). The filter works ms access 2007 smoothly and as intended until it returns no results in my table, and then it pops me with the error. I've tried forcing focus to the textbox in different places throughout the code, but to no avail. If I use the .value or no property for the current textbox, I'm not getting the CURRENT text, but the old text before it was changed, so the filter doesn't work properly. Code Snippet: Private Sub txtVendor_Change() Me.FilterOn = True Me.Filter = _ "((strSearchVendor Like '*" & Me.txtVendor.Text & "*' AND strSearchItem LIKE '*" & Me.txtPartNum & "*'))" Me.txtVendor.SelStart = Len(Me.txtVendor.Text) End Sub It usually pops the error on the last line "Len(Me.txtVendor.Text)", but I've had it do it on the Me.Filter line as well (only when debugging and messing with next statement placement). Any and all help is appreciated. redbe4rd View Public Profile Find More Posts by redbe4rd 09-19-2012, 08:50 AM #2 AccessMSSQL Seasoned Programmer-ette Join Date: May 2012 Location: Los Angeles, California Posts: 636 Thanks: 1 Thanked 110 Times in 109 Posts Re: Runtime Error '2185' when filter returns no results Just use Len(me.txtVendor) You don't need
masks for dates on forms. I usually add code to force the cursor to the beginning of the text box using SelStart. Private Sub txtDate1_GotFocus() Me.txtDate1.SelStart = 0 End Sub I created a form and the above field functioned fine. After I added more controls and code I began to get a Run-time 2185 error -You can't reference a property or method for a control unless the control has the focus. Anyone know what causes this or is my form corrupted in some way? Thanks in advance for any help or insight, -- Scott S Guest, Nov 8, 2007 #1 Advertisements Allen Browne Guest Scott, the only case that comes to mind is where: - You have a form that contains no records, and - No new records can be added. In this case, the detail section goes completely blank. Any controls in the Form Header or Form Footer sections still show, but Access gets confused and can show this error message. More info in the first section of this article: http://allenbrowne.com/bug-06.html -- Allen Browne - Microsoft MVP. Perth, Western Australia Tips for Access users - http://allenbrowne.com/tips.html Reply to group, rather than allenbrowne at mvps dot org. "ScottS" <> wrote in message news:... >I have been using input masks for dates on forms. I usually add code to > force the cursor to the beginning of the text box using SelStart. > > Private Sub txtDate1_GotFocus() > Me.txtDate1.SelStart = 0 > End Sub > > I created a form and the above field functioned fine. After I added more > controls and code I began to get a Run-time 2185 error -You can't > reference a > property or method for a control unless the control has the focus. > > Anyone know what causes this or is my form corrupted in some way? > > Thanks in advance for any help or insight, > -- > Scott S Allen Browne, Nov 9, 2007 #2 Advertisements Linq Adams via AccessMonster.com Guest "You can't reference a property or method for a control unless the control has the focus." So Access is saying that you're trying to do something to ControlA that you can only do when ControlA has focus, and ControlA doesn't have focus! One possibilty that comes to mind, especially when you speak of adding multiple controls and using the i