[AccessD] Trapping Events In A Class (custom events as well as built-in)

Robert,

    Thanks for the clarification. 

    Filter button and search box on navigation bar appear to be a new additions, subsequent to access version 2003 (in which the sample db was developed). I shall investigate further so as to cover this aspect too.

    In the mean time, it would be nice if you could kindly confirm whether the performance is otherwise found OK, if the user carries out filter / search action only through the combination of option group & combo box.

Best wishes,
A.D. Tejpal
------------

  ----- Original Message ----- 
  From: Robert 
  To: 'Access Developers discussion and problem solving' 
  Sent: Tuesday, August 14, 2012 04:34
  Subject: Re: [AccessD] Trapping Events In A Class (custom events as well as built-in)


  I have attached link to a screenshot of the upper forms filter button.
  Inadvertently hitting that button causes the issue, however when the filter
  is reset (show all) it works again.

  Also performing a field search in the lower subform causes the same problem.

  http://i.imgbox.com/ableG8qd.png


  WBR
  Robert
       

  -----Original Message-----
  From: accessd-bounces at databaseadvisors.com
  [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of A.D. Tejpal
  Sent: Monday, August 13, 2012 8:04 AM
  To: Access Developers discussion and problem solving
  Subject: Re: [AccessD] Trapping Events In A Class (custom events as wellas
  built-in)

  Robert,

      Could you kindly explain further? 

      In the upper subform, there is an option group with three toggle
  buttons. Combo box row source depends upon the status of option group. 

      If option group selection is either of first two buttons, the combo box
  acts as a filter for the category specified by option group. For example,
  for first button of option group, combo box drop down list displays author
  names and filter gets applied as per author selected. Similar action is
  performed for Topic, if option group selection happens to be the second
  button.

      On the other hand, if third button of option group is clicked, all
  filters get cleared and the role of combo box gets transformed to that of a
  search box. On selection of desired BookID, the form navigates to
  corresponding record in both subforms. As an added convenience, the
  destination record in bottom subform gets positioned at middle of datasheet
  display window.

      Note: The sample is developed on Access 2003 (Win XP).

  Best wishes,
  A.D. Tejpal
  ------------

    ----- Original Message ----- 
    From: Robert 
    To: 'Access Developers discussion and problem solving' 
    Sent: Monday, August 13, 2012 16:53
    Subject: Re: [AccessD] Trapping Events In A Class (custom events as wellas
  built-in)

    Just a note:

      If you click on the "filter" button on the upper form, it breaks the
    synchronization between the 2 forms. I have not had a chance to
  investigate as I'm heading out the door.

    WBR
    Robert
         

    -----Original Message-----
    From: accessd-bounces at databaseadvisors.com
    [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of A.D. Tejpal
    Sent: Monday, August 13, 2012 4:18 AM
    To: Access Developers discussion and problem solving
    Subject: Re: [AccessD] Trapping Events In A Class (custom events as well
  as built-in)

    J.C.,

        Further to my previous post, sample db named Form_SplitFormSimulated,
    incorporating the concepts discussed so far under this thread, is now
  ready and has been placed at Rogers Access Library. It is in access 2000 file
    format and can be downloaded at the following Link:
    http://www.rogersaccesslibrary.com/forum/forum_topics.asp?FID=45

        A copy of explanatory notes accompanying the sample db is placed
  below, for ready reference. Interested members of this forum might like to test
  it and advise whether anything needs further attention.

    Best wishes,
    A.D. Tejpal
    ------------