Charlotte Foust
charlotte.foust at gmail.com
Mon Mar 24 17:27:29 CDT 2014
Because I was determined to make it work the other way, of course! LOL Actually, I eventually worked out that way of doing it so that the people who will be maintaining it are more likely to understand than WithEvents. I added a loaddata routine to the parent form, removed any master/child links on the subform, and allowed the subform to search in it's (snapshot) recordset for the desired record and pass the key into the loadData routine on the parent form. It isn't elegant but these guys are engineers, not database developers, and they'll be able to understand this. Charlotte. On Mon, Mar 24, 2014 at 1:48 PM, Salakhetdinov Shamil <mcp2004 at mail.ru>wrote: > Hi Charlotte -- > > Why not just define a > > Public Sub ProcessEvent(ByVal eventName As String, ParamArray eventArgs()) > MsgBox eventName & ", Params Count = " & UBound(eventArgs) + 1 ' test > End Sub > > in the Parent form and call it from a subform like that > > Me.Parent.ProcessEvent "Test event", "Prm1", 123.45 ' test call > -- Shamil > > > Mon, 24 Mar 2014 13:23:54 -0700 from Charlotte Foust < > charlotte.foust at gmail.com>: > >I know I've done this before but it probably required a class, which I > >hesitate to use in this app. Has anyone else had problems raising and > >sinking events between forms in Access 2010/2013? > > > >Charlotte > >-- > >AccessD mailing list > >AccessD at databaseadvisors.com > >http://databaseadvisors.com/mailman/listinfo/accessd > >Website: http://www.databaseadvisors.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >