Losing Cursor on Form after Set Me.Recordset = Rs

[ussmex]

Greetings,

I'm experiencing the same problem as in the post titled "Loosing Cursor on Form after Set Me.Recordset = Rs".

In my VBA code I set the recordset, then setfocus on a textbox. When I "Debug.Print Screen.ActiveControl.Name" it names the text box, but the cursor doesn't show in that textbox, and typing on the keyboard has no effect anywhere on the form window. In order for to enter text via the keyboard I must mouse-click the textbox.



In the aforementioned post the poster mentions his workaround:
After setting focus on the textbox, he uses SendKeys:
SendKeys "%"
SendKeys "{ESC}"
This works. After the SendKeys runs, the cursor is showing in the textbox, and entry via keyboard is available.

Does know of a status in which SetFocus has functioned properly, but the cursor is unavailable? Is there a Windows property I can reference to force the cursor into the textbox?

Thank you!

[CJ_London]

Would help if you show your actual code or better still upload a copy of your database - remove all tables/forms/etc not relevant to you question, then compact and zip

[Micron]

Have never seen this. If we try to replicate it, it would help to know where your code is - standard module or form module. It might matter.

[ussmex]

The code to retrieve the ADODB recordset (EXEC stored procedure) is in a standard module. That code is triggered in a Private Function on a form module, and triggers by a Click event in a listbox.

Previously, when I was using a linked table as the RecordSource for the form, the cursor was available in the textbox after SetFocus. It is since I have begun trying this new way of populating data using recordsets that this issue has been occurring.

Private Function SelectAllbyOrgID()
    'triggered on lstSearchResults_Click
    strSQL = "EXEC Org.sp_tblOrgSelectAll " & Me.lstSearchResults
    OpenMyRecordset rs, strSQL
    Set Me.Recordset = rs
    Debug.Print Screen.ActiveControl.Name
    Me.txtOrgNameSearch.SetFocus
End Function

[CJ_London]

so it is an ado recordset, not dao. That probably explains it - access forms are designed to work with dao - they will work with ado but some features do not work. Certainly the filter and sort features will generate an error with ado, quite possible your problem is another 'feature' that does not work.