[AccessD] Combo Boxes On continuous Forms (was: quick help needed)

Combo Boxes On continuous Forms
=========================

    An alternative solution aimed at preventing blank display on combo boxes in continuous forms, is demonstrated in my sample db named Form_ContWithCascadedCombo. It is available at Rogers Access Library (other developers library). Link:
http://www.rogersaccesslibrary.com/forum/forum_topics.asp?FID=45
 
    This approach is based upon having all the bound values always in the look-up list, but ensuring that only the pertinent values are selectable and are displayed at top
    
    Supplementary Notes:
    ----------------------
    On a continuous form, so long as the bound column of a bound combo box is the same as the column under display, there is no confusion or problem (e.g. display going blank). However, if displayed column is different from the bound column, and row source is dynamically filtered, the well known phenomenon of blanking out of display in all or some of the combo boxes other than the active one, is encountered. 

    This is on account of the fact that what you see displayed is not the actual value held by the field (acting as control source for the combo box) but an interpretation based upon value held in the bound column. As a result, whenever the row source no longer contains certain values in the bound column, such of the records where combo boxes hold any of the missing values, can no longer be interpreted and the display goes blank. It is to be noted that the actual values held in such records are not really lost. These are still intact, but simply not getting interpreted and displayed.

Best wishes,
A.D. Tejpal
------------
  ----- Original Message ----- 
  From: Gary Kjos 
  To: Access Developers discussion and problem solving 
  Sent: Friday, June 18, 2010 03:29
  Subject: Re: [AccessD] quick help needed


  Yeah it sounds a lot better than what I ended up with which has a text
  box on top of the second combo box and some requery's in the on
  current and after update for the first combo box. I'll have to look at
  this tomorrow. This application is one I started working on a year ago
  and it's been sitting idle as I've had other bigger fish to fry but
  now the intended user has forced me to pick it up again.

  Thanks for Sharing David.

  GK

  On Thu, Jun 17, 2010 at 4:14 PM, Stuart McLachlan
  <stuart at lexacorp.com.pg> wrote:
  > Damn, that's neat.
  >
  > Why didn't you post that simple concept years ago on the list. I could have used variants of it
  > lots of times in the past. :-(
  >
  > --
  > Stuart
  >
  >
  > On 17 Jun 2010 at 13:17, David McAfee wrote:
  >
  >> Gary, IIRC, one thing I did before in regards to cascading comboboxes
  >> in a continuous form (wow, a tongue twister) was
  >> to have two different rowsources for the 2nd combo box.
  >>
  >> The normal, or OnCurrent combo would list everything (not really cascading) and
  >> in the 2nd combo's OnEnter event I change the rowsource to reflect
  >> that of the first.
  >> The OnChange event would change it back to the "everything"
  >>
  >> something like this:
  >> OnEnter:
  >> Me.SecondComo.Rowsource = "EXEC stpShowFilteredDate " & NZ(Me.FirstCombo,0)
  >>
  >> OnChange:
  >> Me.SecondComo.Rowsource = "EXEC stpShowAllData"
  >>
  >>
  >>
  >> On Thu, Jun 17, 2010 at 12:59 PM, Gary Kjos <garykjos at gmail.com> wrote:
  >> > That's what we are here for. ;-) Glad you got it figured out.
  >> >
  >> > I'm actually working on an Access Development project right now. First
  >> > time in YEARS. Strugling through cascading combo boxes on a continuous
  >> > subform. Grrr. I think I have it now. With some magic putting text
  >> > booxes on top of combo boxes and "On Current Requery" code.
  >> >
  >> > GK.