--
Fred
"Dorian C. Chalom" <DCh...@Comcast.net> wrote in message
news:esdIzwwk...@TK2MSFTNGP04.phx.gbl...
Thank you for taking the time...
It is really strange...
On the form that does not work I coded the grid through code.
I then create a new form of the Combo/Grid and it works the way it should.
So i put a button on the form that does not work to open the form that does
work
The form that does work does work but also the grid on the form that does
not work updates and works as well but it is read only...
With all that said what does happen on the form that does not work is that
when you change a value in the combo box it does move the cursor to the
first record for the value in the combo box but it does not only show the
records for the value selected in the combo box. You can still scan the
whole table.
So my question is how do i limit it to only display the values for the value
in the combo box?
Thanks again for your time...
"Fred Taylor" <fta...@mvps.org!REMOVE> wrote in message
news:%23P1gDM7...@TK2MSFTNGP05.phx.gbl...
Give up?
"Fred Taylor" <fta...@mvps.org!REMOVE> wrote in message
news:%23P1gDM7...@TK2MSFTNGP05.phx.gbl...
--
Fred
"Dorian C. Chalom" <DCh...@Comcast.net> wrote in message
news:%23KMorwt...@TK2MSFTNGP02.phx.gbl...
What is bafling to me is why the combo/grid I created from code will not
work like the one I created on a seperate form that works the way it should.
In the time being what I did was just remove the combo/grid from the form
that does not work and just put a button onto the form that does work.
That seems to work for now but not how I want it.
"Fred Taylor" <fta...@mvps.org!REMOVE> wrote in message
news:uVacNa7l...@TK2MSFTNGP04.phx.gbl...
Dorian,
It is hard to decipher what your scenario really is.
But, that aside,
I have written an application based on a form.
This form is driven by selecting a "Set Filter To" value from a combo-
box.
This Combo-box is record-sourced by a local view which Selects a field
on a grouped by this field. Then the value of the selected field in
placed in a thisform.memvar which is available to anything in the
form.
The Combo-box.validate() sets focus to another cmdButton.click().
Now, the combo-box is validated and inactive, and the cmdButton.Click
() is active.
This cmdButton checks to see if there is a value (from Combo-box) in
the thisform.memvar. If so, then it calls the PageFrame1.Page1.click
() to begin checking, and if ok, then it selects the "parameterized"
local view used as the recordsource for the Grid (called lvGrid), and
does a Requery() to populate the lvGrid according to the
thisform.memvar (which is the parameter required).
Still with me?
I had much frustration with the Combo-box calling anything which
operated within the Combo-box container, as it would initiate a
"stack" of methods down and backup, not waiting for me to use the
PageFrame1.Page1.Grid1, etc.
The idea I worked out was to use the Combo-box
for (1) the simple task of placing a selected value
into a thisform.memvar,
then (2) shifting focus out to a cmdButton
which operates in a predictable and controllable manner.
You know, of course, that you can made the cmdButton InVisible,
and it still does its job OK. I have several InVisible cmdButtons
sitting 'on' the form, which function reliable to calculate and
transfer control to Visible objects (like PageFrame.Pages and Grids.)
I guess that was a "work-around" but it has worked for several years
now,
in several variations, in different applications.
Hope that helps.