Re: Trouble with combo Box selecting new client



Bob Alston wrote:
Salad wrote:

Bob Alston wrote:

Salad wrote:

Bob Alston wrote:

Having intermittant problems with a combo box I use to allow users to select a new client.

I am using Access 2003 sp3 and an Access2002/2003 file format.



Have you applied the hotfix to sp3?

My clients run MDE versions of the software. About 6 meg in size.
It is a FR/BE environment with the data on a Netware server.

I initially open the form, which happens to have multiple tabs and multiple subforms, using a filter. that way only records for one client is retrieved from the back end (of course in addition to the indices needed). Approx 6000 clients in the database.

I use my drop down list box to let my user select another client.
In the on click event, I obtain the key needed for the filter, assemble the filter, cause a requery and blank out the bound field in the combo box so it is ready for another selection. Normally this works just fine.

Three types of issues I have found:

1) sometimes, the drop down list box displays the client list correctly and I can scroll down to various clients. But if I select via a left click or press enter when a client is highlighted, nothing happens.
Also if I start to type in a client name, the list does not move to show only clients whose last name begins with that name.

a)This happened to one client running Windows XP with Access 2003 without any SPs. I am upgrading her to SP3 to see what happens.

b) I have had this happen on my development PC (Vista ultimate w/ Access 2003 sp3) in the uncompiled version but work just fine in the compiled version.

2) One case today was a user who had Windows XP and SP3 but when the form opened, she could not see any of the subforms. Like the selection of the client in the top level form was bogus (but it is a standard starting point that normally works). I tried one of my older versions and that worked.

My code for the on got focus event and on click events are below:

Private Sub RecordSelector_GotFocus()
RecordSelector.Dropdown
End Sub

Private Sub RecordSelector_Click()
'DoCmd.RunCommand acCmdSaveRecord
'DoCmd.RunCommand acCmdRefresh
''RecordSelector.Requery
'If IsNull(RecordSelector) Or Len(RecordSelector) = 0 Then
' RecordSelector = 0
'End If
'Client_Number.SetFocus
'DoCmd.FindRecord RecordSelector, , True, , True

Me.Filter = "[cl_lname_1] = '" & Me.RecordSelector.Column(1) & "' and [cl_fname_1] = '" & Me.RecordSelector.Column(2) & "' and [cl_ssn] = '" & Me.RecordSelector.Column(3) & "'"

Me.RecordSelector = Null

Me.Requery
End Sub


My combo box is bound on column 1 and has this Rowsource:

SELECT DISTINCT tbl_Client_data_additional.cl_lname_1, tbl_Client_data_additional.cl_lname_1, tbl_Client_Data_Additional.cl_fname_1, tbl_Client_data_Additional.cl_ssn FROM tbl_Client_Data_Additional ORDER BY tbl_Client_Data_Additional.cl_lname_1, tbl_Client_Data_Additional.cl_fname_1;

It is LimitToList=yes



My code to open the form initially has this code for the on-click event

Private Sub Command46_Click()
On Error GoTo Err_Command46_Click

Dim stDocName As String
Dim stLinkCriteria As String
stLinkCriteria = "[client_number] = 0 and [cl_lname_1] = 'Affab'"
stDocName = "frm_ClientProfile"
DoCmd.OpenForm stDocName, , , stLinkCriteria

Exit_Command46_Click:
Exit Sub

Err_Command46_Click:
MsgBox Err.Description
Resume Exit_Command46_Click

End Sub


The client named is in the database and normally displays without problem.

suggestions for things I should look at??

bob


Exactly what hotfix?


Here's a link to the hotfix for sp3.
http://support.microsoft.com/kb/945674

Thanks. I will install.

However, it does not seem to right on point for the problem I have been experiencing. Have you seen this hotfix resolve issues like mine?

bob

No. I was avoiding the SP3 upgrade but Windows Update installed it on my PC automatically. Then I experienced errors (unrelated to yours). So I installed the hotfix and the errors disappeared. Since you experienced errors with SP3, and I did not know if you had applied the hotfix, and others had problems with combos with SP3 w/o the hotfix, perhaps the error you experienced would also disappear. Not guaranteed, but it may help others in helping you out if it were known you had done both SP3 and hotfix.
.



Relevant Pages

  • Re: **Urgent** New Edit in Datasheet error occurring on proven WSS
    ... We actually upgraded our WSS 2.0 to SP3 and that caused the issue on the ... client machines running Office 2K3. ... the functionality I decided to attempt some client-based fixes. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Trouble with combo Box selecting new client
    ... I am using Access 2003 sp3 and an Access2002/2003 file format. ... Have you applied the hotfix to sp3? ... that way only records for one client is retrieved from the back end. ... it does not seem to right on point for the problem I have been experiencing. ...
    (comp.databases.ms-access)
  • Re: Corrupt field in table?
    ... I have no formattting in my combobox. ... Just two fields PartID and PartDesc, ... I just updated my version of Access to SP3. ... any chance your client was updated to SP3 (only recently ...
    (microsoft.public.access.forms)
  • Re: RWW Errors Make No Sense
    ... Is this issue related to SP3 in general and not an SP3 MCE ... Try resetting the IE settings to their previous levels and then follow ... remote into their office computer from home via RWW ... They then "connect to client computer". ...
    (microsoft.public.windows.server.sbs)
  • Re: Corrupt field in table?
    ... Allen Browne - Microsoft MVP. ... I just updated my version of Access to SP3. ... any chance your client was updated to SP3 (only recently ... Also we tried to uninstall the Access ...
    (microsoft.public.access.forms)

Loading