H
HermitCrab
I have design an Access 2003 Project that has a customer/ contact form
that uses an unbound combo to search and display customer records. The
form is bound to the customer table and the bound column of the combo
is the customerid, which is the primary key.
In Access 2003 this worked fine.
In Access 2007 the form is not filtered. The original record is still
display regardless of the selection in the combo.
The back end is SQL Server 2008 Express.
The code for the unbound combo is:
Private Sub cboCustomerSearch_AfterUpdate()
Me.Filter = "CustomerID = '" & Me.cboCustomerSearch & "'"
Me.FilterOn = True
End Sub
This is what works in Access 2003.
Are there defaults or other settings in Access 2007 that would
influence this behavior?
I can provide more details if it would help...
that uses an unbound combo to search and display customer records. The
form is bound to the customer table and the bound column of the combo
is the customerid, which is the primary key.
In Access 2003 this worked fine.
In Access 2007 the form is not filtered. The original record is still
display regardless of the selection in the combo.
The back end is SQL Server 2008 Express.
The code for the unbound combo is:
Private Sub cboCustomerSearch_AfterUpdate()
Me.Filter = "CustomerID = '" & Me.cboCustomerSearch & "'"
Me.FilterOn = True
End Sub
This is what works in Access 2003.
Are there defaults or other settings in Access 2007 that would
influence this behavior?
I can provide more details if it would help...