In Access 2007 I have encountered instances where Me.Filter = "... " fails to operate for a split form. Using a reference set to the form object e.g. frmObj.Filter = "...." also fails to operate.
(In both these cases .Filter = " ... " is followed by .FilterOn = True. and in both cases a debug statement shows that the Filter and FilterOn have been updated as entered. However, using Forms![formname]![subformname].form.Filter = ".." works. I am already using frmobj.RecordSo urce as a primary filter so switching to using the RecordSource is not a viable alternative. (Me.recordSourc e = "..." and frmObj.RecordSo urce = " ... " both work for the problem form. I have tried creating a new form without success.
The facility using frmObj.Filter is generic and hence I cannot use the Forms! address.
Has anyone come across Me.Filter failing and resolving why , especially as other forms/subforms in the same application work using the Me/frmObj.Filter syntax.
(In both these cases .Filter = " ... " is followed by .FilterOn = True. and in both cases a debug statement shows that the Filter and FilterOn have been updated as entered. However, using Forms![formname]![subformname].form.Filter = ".." works. I am already using frmobj.RecordSo urce as a primary filter so switching to using the RecordSource is not a viable alternative. (Me.recordSourc e = "..." and frmObj.RecordSo urce = " ... " both work for the problem form. I have tried creating a new form without success.
The facility using frmObj.Filter is generic and hence I cannot use the Forms! address.
Has anyone come across Me.Filter failing and resolving why , especially as other forms/subforms in the same application work using the Me/frmObj.Filter syntax.