Are you saying that MS Access now has triggers?

Bill E. Hollywood, FL wrote:
Yes, I was surprised by this as well. It seems they were introduced in
A2010. They're called "data macros" I think.

I took a look and this functionality is impressive. I'll have to do
some experiments. I also noticed that they finally cleaned up the
problem with derived tables inside queries. For example, the query

SELECT ID Name
FROM (SELECT CustomerID AS ID, CustomerName AS Name FROM Customers) Q

would always be changed by Access to read

SELECT ID Name
FROM [SELECT CustomerID AS ID, CustomerName AS Name FROM Customers]. Q

and this []. notation would cause problems. Thank goodness it's
fixed.

Just to end this thread, I eventually decided to create a function in
Visual Basic that I could call from a macro that would reset the
recordsource of a form or subform contained in a form. The code is
below. In this way I no longer need to do "fancy" filtering. Also,
this is the way I would naturally do things when writing Visual Basic,
so why not do it the same way with macros?

Function SetFormRecordsource(FormName As String, SubformName As
String, Query As String)
'Change the recordsource for a form or subform
On Error GoTo Trapper
Dim frm As Form

If SubformName = "" Then
Set frm = Forms(FormName)
Else
Set frm = Forms(FormName).Controls(SubformName).Form
End If

If frm.RecordSource <> Query Then
frm.RecordSource = Query
'frm.Requery
Else
frm.Requery
End If
Set frm = Nothing
Exit Function
Trapper:
'MsgBox Err.Description
Set frm = Nothing
Exit Function
End Function