Option Group Quits after Filter Removed

[Guest]

I don't have the database available at the moment for all specifics, but my
general question is, why would an option group frame named DaysAhead (3 radio
buttons 1 = 30, 2 = 60, 3 = 90 (days) )work perfectly to regulate displayed
date ranges on a continuous form but quit working when any data field is
FilterBySelection then restored to full view through RemoveFilterSort? This
is on an Access2002 dbase.
The DaysAhead frame is used to fill two date fields: Date1 and Date2.
Date1 is always Now() and Date2 is Now() + DaysAhead.Value (30, 60 or 90).
Date1 and Date2 are the date criteria on the Expiration form's qryExpiration
query, which are requried in the AfterUpdate Event of the DaysAhead.

 

[MacDermott]

Could you be more specific about "quit working"?

 

[Guest]

Yes. After a successful date range filtering using one of the radio buttons,
(30 days from Now() to Now()+30 being the default), a user can then
single-click inside the Analyst field to select a specific analyst, then
successfully click another radio button within the DaysAhead option frame to
view 30, 60 or 90 days ahead for that analyst. All is well until they
double-click the Analyst field to RemoveFilterSort, which works, but for some
reason the radio button is rendered "dead" at that point. No error or
anything except a "calculating" indicator down at the bottom left of the
window, resulting in no further filtering. Only when the form is reopened
will the original filter be enabled again. This is on a tab control page as a
subform called frmSubfrmExpirations30 bound to qryExpirations query where the
query date has the parameter Between
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder1] and
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder2].

I've tried placing the Option Group and the DateHolder1 and DateHolder2
fields on the main form as well as the subform but end up with the same
results.

 

[MacDermott]

Could you post the code for the single- and double-click events for the
Analyst control?

Yes. After a successful date range filtering using one of the radio buttons,
(30 days from Now() to Now()+30 being the default), a user can then
single-click inside the Analyst field to select a specific analyst, then
successfully click another radio button within the DaysAhead option frame to
view 30, 60 or 90 days ahead for that analyst. All is well until they
double-click the Analyst field to RemoveFilterSort, which works, but for some
reason the radio button is rendered "dead" at that point. No error or
anything except a "calculating" indicator down at the bottom left of the
window, resulting in no further filtering. Only when the form is reopened
will the original filter be enabled again. This is on a tab control page as a
subform called frmSubfrmExpirations30 bound to qryExpirations query where the
query date has the parameter Between
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder1] and
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder2].

I've tried placing the Option Group and the DateHolder1 and DateHolder2
fields on the main form as well as the subform but end up with the same
results.

Could you be more specific about "quit working"?

but
my (3
radio

 

[Guest]

Private Sub Analyst_Click()
RunCommand acCmdFilterBySelection

Private Sub Analyst_DblClick(Cancel As Integer)
Me.Filter = ""

On the Double-Click I've also used RunCommand acCmdRemoveFilterSort.
Both Click and Double-Click functions seem to work perfectly. I've used
Me.Requery in the Double-Click code after the sort as well. The filtering
and unfiltering processes appear to be working fine.

It's the FrameDaysAhead requerying that seems to take a coffee break after
the filter removal until I close the main form and reopen it again.

Could you post the code for the single- and double-click events for the
Analyst control?

Yes. After a successful date range filtering using one of the radio buttons,
(30 days from Now() to Now()+30 being the default), a user can then
single-click inside the Analyst field to select a specific analyst, then
successfully click another radio button within the DaysAhead option frame to
view 30, 60 or 90 days ahead for that analyst. All is well until they
double-click the Analyst field to RemoveFilterSort, which works, but for some
reason the radio button is rendered "dead" at that point. No error or
anything except a "calculating" indicator down at the bottom left of the
window, resulting in no further filtering. Only when the form is reopened
will the original filter be enabled again. This is on a tab control page as a
subform called frmSubfrmExpirations30 bound to qryExpirations query where the
query date has the parameter Between
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder1] and
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder2].

I've tried placing the Option Group and the DateHolder1 and DateHolder2
fields on the main form as well as the subform but end up with the same
results.

Could you be more specific about "quit working"?

I don't have the database available at the moment for all specifics, but
my
general question is, why would an option group frame named DaysAhead (3
radio
buttons 1 = 30, 2 = 60, 3 = 90 (days) )work perfectly to regulate
displayed
date ranges on a continuous form but quit working when any data field is
FilterBySelection then restored to full view through RemoveFilterSort?
This
is on an Access2002 dbase.
The DaysAhead frame is used to fill two date fields: Date1 and Date2.
Date1 is always Now() and Date2 is Now() + DaysAhead.Value (30, 60 or 90).
Date1 and Date2 are the date criteria on the Expiration form's
qryExpiration
query, which are requried in the AfterUpdate Event of the DaysAhead.

 

[MacDermott]

What is the code which runs when you click an option button in
FrameDaysAhead?

Private Sub Analyst_Click()
RunCommand acCmdFilterBySelection

Private Sub Analyst_DblClick(Cancel As Integer)
Me.Filter = ""

On the Double-Click I've also used RunCommand acCmdRemoveFilterSort.
Both Click and Double-Click functions seem to work perfectly. I've used
Me.Requery in the Double-Click code after the sort as well. The filtering
and unfiltering processes appear to be working fine.

It's the FrameDaysAhead requerying that seems to take a coffee break after
the filter removal until I close the main form and reopen it again.

Could you post the code for the single- and double-click events for the
Analyst control?

Yes. After a successful date range filtering using one of the radio buttons,
(30 days from Now() to Now()+30 being the default), a user can then
single-click inside the Analyst field to select a specific analyst, then
successfully click another radio button within the DaysAhead option

frame
to

view 30, 60 or 90 days ahead for that analyst. All is well until they
double-click the Analyst field to RemoveFilterSort, which works, but

for
some

reason the radio button is rendered "dead" at that point. No error or
anything except a "calculating" indicator down at the bottom left of the
window, resulting in no further filtering. Only when the form is reopened
will the original filter be enabled again. This is on a tab control

page
as a

subform called frmSubfrmExpirations30 bound to qryExpirations query

where
the

query date has the parameter Between
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder1] and
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder2].

I've tried placing the Option Group and the DateHolder1 and DateHolder2
fields on the main form as well as the subform but end up with the same
results.


:

Could you be more specific about "quit working"?

I don't have the database available at the moment for all

specifics,
but

my
general question is, why would an option group frame named

DaysAhead
(3

radio
buttons 1 = 30, 2 = 60, 3 = 90 (days) )work perfectly to regulate
displayed
date ranges on a continuous form but quit working when any data

field
is

FilterBySelection then restored to full view through RemoveFilterSort?
This
is on an Access2002 dbase.
The DaysAhead frame is used to fill two date fields: Date1 and Date2.
Date1 is always Now() and Date2 is Now() + DaysAhead.Value (30, 60

or
90).

Date1 and Date2 are the date criteria on the Expiration form's
qryExpiration
query, which are requried in the AfterUpdate Event of the DaysAhead.

 

[Guest]

Private Sub FrameDaysAhead_Click()
Select Case FrameDaysAhead.Value
Case 1
[DayHolder1] = Now()
[DayHolder2] = Now() + 30
Me.Requery
Case 2
[DayHolder1] = Now()
[DayHolder2] = Now() + 60
Me.Requery
Case 3
[DayHolder1] = Now()
[DayHolder2] = Now() + 90
Me.Requery
End Select
End Sub

What is the code which runs when you click an option button in
FrameDaysAhead?

Private Sub Analyst_Click()
RunCommand acCmdFilterBySelection

Private Sub Analyst_DblClick(Cancel As Integer)
Me.Filter = ""

On the Double-Click I've also used RunCommand acCmdRemoveFilterSort.
Both Click and Double-Click functions seem to work perfectly. I've used
Me.Requery in the Double-Click code after the sort as well. The filtering
and unfiltering processes appear to be working fine.

It's the FrameDaysAhead requerying that seems to take a coffee break after
the filter removal until I close the main form and reopen it again.

Could you post the code for the single- and double-click events for the
Analyst control?

Yes. After a successful date range filtering using one of the radio
buttons,
(30 days from Now() to Now()+30 being the default), a user can then
single-click inside the Analyst field to select a specific analyst, then
successfully click another radio button within the DaysAhead option frame
to
view 30, 60 or 90 days ahead for that analyst. All is well until they
double-click the Analyst field to RemoveFilterSort, which works, but for
some
reason the radio button is rendered "dead" at that point. No error or
anything except a "calculating" indicator down at the bottom left of the
window, resulting in no further filtering. Only when the form is reopened
will the original filter be enabled again. This is on a tab control page
as a
subform called frmSubfrmExpirations30 bound to qryExpirations query where
the
query date has the parameter Between
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder1] and
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder2].

I've tried placing the Option Group and the DateHolder1 and DateHolder2
fields on the main form as well as the subform but end up with the same
results.


:

Could you be more specific about "quit working"?

I don't have the database available at the moment for all specifics,
but
my
general question is, why would an option group frame named DaysAhead
(3
radio
buttons 1 = 30, 2 = 60, 3 = 90 (days) )work perfectly to regulate
displayed
date ranges on a continuous form but quit working when any data field
is
FilterBySelection then restored to full view through RemoveFilterSort?
This
is on an Access2002 dbase.
The DaysAhead frame is used to fill two date fields: Date1 and Date2.
Date1 is always Now() and Date2 is Now() + DaysAhead.Value (30, 60 or
90).
Date1 and Date2 are the date criteria on the Expiration form's
qryExpiration
query, which are requried in the AfterUpdate Event of the DaysAhead.

 

[MacDermott]

Is FrameDaysAhead on the main form, or the subform?

Private Sub FrameDaysAhead_Click()
Select Case FrameDaysAhead.Value
Case 1
[DayHolder1] = Now()
[DayHolder2] = Now() + 30
Me.Requery
Case 2
[DayHolder1] = Now()
[DayHolder2] = Now() + 60
Me.Requery
Case 3
[DayHolder1] = Now()
[DayHolder2] = Now() + 90
Me.Requery
End Select
End Sub

What is the code which runs when you click an option button in
FrameDaysAhead?

Private Sub Analyst_Click()
RunCommand acCmdFilterBySelection

Private Sub Analyst_DblClick(Cancel As Integer)
Me.Filter = ""

On the Double-Click I've also used RunCommand acCmdRemoveFilterSort.
Both Click and Double-Click functions seem to work perfectly. I've used
Me.Requery in the Double-Click code after the sort as well. The filtering
and unfiltering processes appear to be working fine.

It's the FrameDaysAhead requerying that seems to take a coffee break after
the filter removal until I close the main form and reopen it again.


:

Could you post the code for the single- and double-click events for the
Analyst control?

Yes. After a successful date range filtering using one of the radio
buttons,
(30 days from Now() to Now()+30 being the default), a user can then
single-click inside the Analyst field to select a specific

analyst,
then

successfully click another radio button within the DaysAhead

option
frame

to
view 30, 60 or 90 days ahead for that analyst. All is well until they
double-click the Analyst field to RemoveFilterSort, which works,

but
for

some
reason the radio button is rendered "dead" at that point. No error or
anything except a "calculating" indicator down at the bottom left

of
the

window, resulting in no further filtering. Only when the form is reopened
will the original filter be enabled again. This is on a tab

control
page

as a
subform called frmSubfrmExpirations30 bound to qryExpirations

query
where

the
query date has the parameter Between
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder1] and
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder2].

I've tried placing the Option Group and the DateHolder1 and DateHolder2
fields on the main form as well as the subform but end up with the same
results.


:

Could you be more specific about "quit working"?

I don't have the database available at the moment for all specifics,
but
my
general question is, why would an option group frame named DaysAhead
(3
radio
buttons 1 = 30, 2 = 60, 3 = 90 (days) )work perfectly to regulate
displayed
date ranges on a continuous form but quit working when any

data
field

is
FilterBySelection then restored to full view through RemoveFilterSort?
This
is on an Access2002 dbase.
The DaysAhead frame is used to fill two date fields: Date1

and
Date2.

Date1 is always Now() and Date2 is Now() + DaysAhead.Value

(30, 60
or

90).
Date1 and Date2 are the date criteria on the Expiration form's
qryExpiration
query, which are requried in the AfterUpdate Event of the DaysAhead.

 

[Guest]

FrameDaysAhead is on the main form, which does its job, even when the
individual Analyst is filtered.

For instance, if Analyst "Smith" is the person of focus and has her 30 days
items showing, when I hit the 60 or 90 day radio button, the records change
accordingly. As well, when no one is filtered, the entire subform responds
with the desired date ranges.

All is well until the FilterBySelection is removed either by the built-in
Access toolbar RemoveFilterSort lightning bolt button or the double-click
Analyst field of the subform with the Me.Filter = "" code. Same zero
response result until the hidden binding is flushed when the entire
Workstation1 form is closed and reopened.

Is FrameDaysAhead on the main form, or the subform?

Private Sub FrameDaysAhead_Click()
Select Case FrameDaysAhead.Value
Case 1
[DayHolder1] = Now()
[DayHolder2] = Now() + 30
Me.Requery
Case 2
[DayHolder1] = Now()
[DayHolder2] = Now() + 60
Me.Requery
Case 3
[DayHolder1] = Now()
[DayHolder2] = Now() + 90
Me.Requery
End Select
End Sub

What is the code which runs when you click an option button in
FrameDaysAhead?

Private Sub Analyst_Click()
RunCommand acCmdFilterBySelection

Private Sub Analyst_DblClick(Cancel As Integer)
Me.Filter = ""

On the Double-Click I've also used RunCommand acCmdRemoveFilterSort.
Both Click and Double-Click functions seem to work perfectly. I've used
Me.Requery in the Double-Click code after the sort as well. The filtering
and unfiltering processes appear to be working fine.

It's the FrameDaysAhead requerying that seems to take a coffee break after
the filter removal until I close the main form and reopen it again.


:

Could you post the code for the single- and double-click events for the
Analyst control?

Yes. After a successful date range filtering using one of the radio
buttons,
(30 days from Now() to Now()+30 being the default), a user can then
single-click inside the Analyst field to select a specific analyst,
then
successfully click another radio button within the DaysAhead option
frame
to
view 30, 60 or 90 days ahead for that analyst. All is well until they
double-click the Analyst field to RemoveFilterSort, which works, but
for
some
reason the radio button is rendered "dead" at that point. No error or
anything except a "calculating" indicator down at the bottom left of
the
window, resulting in no further filtering. Only when the form is
reopened
will the original filter be enabled again. This is on a tab control
page
as a
subform called frmSubfrmExpirations30 bound to qryExpirations query
where
the
query date has the parameter Between
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder1] and
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder2].

I've tried placing the Option Group and the DateHolder1 and
DateHolder2
fields on the main form as well as the subform but end up with the
same
results.


:

Could you be more specific about "quit working"?

I don't have the database available at the moment for all
specifics,
but
my
general question is, why would an option group frame named
DaysAhead
(3
radio
buttons 1 = 30, 2 = 60, 3 = 90 (days) )work perfectly to regulate
displayed
date ranges on a continuous form but quit working when any data
field
is
FilterBySelection then restored to full view through
RemoveFilterSort?
This
is on an Access2002 dbase.
The DaysAhead frame is used to fill two date fields: Date1 and
Date2.
Date1 is always Now() and Date2 is Now() + DaysAhead.Value (30, 60
or
90).
Date1 and Date2 are the date criteria on the Expiration form's
qryExpiration
query, which are requried in the AfterUpdate Event of the
DaysAhead.

 

[MacDermott]

Sorry to be so thick about this:
FrameDaysAhead is on the main form; I presume that DateHolder1 and
DateHolder2 are also on the main form?
But the query uses a parameter of
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder1]
which is looking for the DateHolder1 control on the subform?

FrameDaysAhead is on the main form, which does its job, even when the
individual Analyst is filtered.

For instance, if Analyst "Smith" is the person of focus and has her 30 days
items showing, when I hit the 60 or 90 day radio button, the records change
accordingly. As well, when no one is filtered, the entire subform responds
with the desired date ranges.

All is well until the FilterBySelection is removed either by the built-in
Access toolbar RemoveFilterSort lightning bolt button or the double-click
Analyst field of the subform with the Me.Filter = "" code. Same zero
response result until the hidden binding is flushed when the entire
Workstation1 form is closed and reopened.

Is FrameDaysAhead on the main form, or the subform?

Private Sub FrameDaysAhead_Click()
Select Case FrameDaysAhead.Value
Case 1
[DayHolder1] = Now()
[DayHolder2] = Now() + 30
Me.Requery
Case 2
[DayHolder1] = Now()
[DayHolder2] = Now() + 60
Me.Requery
Case 3
[DayHolder1] = Now()
[DayHolder2] = Now() + 90
Me.Requery
End Select
End Sub

:

What is the code which runs when you click an option button in
FrameDaysAhead?

Private Sub Analyst_Click()
RunCommand acCmdFilterBySelection

Private Sub Analyst_DblClick(Cancel As Integer)
Me.Filter = ""

On the Double-Click I've also used RunCommand acCmdRemoveFilterSort.
Both Click and Double-Click functions seem to work perfectly.

I've
used

Me.Requery in the Double-Click code after the sort as well. The filtering
and unfiltering processes appear to be working fine.

It's the FrameDaysAhead requerying that seems to take a coffee

break
after

the filter removal until I close the main form and reopen it again.


:

Could you post the code for the single- and double-click events

for
the

Analyst control?

Yes. After a successful date range filtering using one of the radio
buttons,
(30 days from Now() to Now()+30 being the default), a user can then
single-click inside the Analyst field to select a specific analyst,
then
successfully click another radio button within the DaysAhead option
frame
to
view 30, 60 or 90 days ahead for that analyst. All is well

until
they

double-click the Analyst field to RemoveFilterSort, which

works,
but

for
some
reason the radio button is rendered "dead" at that point. No error or
anything except a "calculating" indicator down at the bottom

left
of

the
window, resulting in no further filtering. Only when the form is
reopened
will the original filter be enabled again. This is on a tab control
page
as a
subform called frmSubfrmExpirations30 bound to qryExpirations query
where
the
query date has the parameter Between

Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder1]
and

Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder2].

I've tried placing the Option Group and the DateHolder1 and
DateHolder2
fields on the main form as well as the subform but end up with the
same
results.


:

Could you be more specific about "quit working"?

I don't have the database available at the moment for all
specifics,
but
my
general question is, why would an option group frame named
DaysAhead
(3
radio
buttons 1 = 30, 2 = 60, 3 = 90 (days) )work perfectly to regulate
displayed
date ranges on a continuous form but quit working when any data
field
is
FilterBySelection then restored to full view through
RemoveFilterSort?
This
is on an Access2002 dbase.
The DaysAhead frame is used to fill two date fields:

Date1
and

Date2.
Date1 is always Now() and Date2 is Now() + DaysAhead.Value (30, 60
or
90).
Date1 and Date2 are the date criteria on the Expiration form's
qryExpiration
query, which are requried in the AfterUpdate Event of the
DaysAhead.

 

[Guest]

Please forgive me! You're not thick at all. I'm just living in the past.
The initial incarnation of the database had the framedaysahead as well as the
dateholder fields on the main form.

Due to the problem I was encountering, I thought I would relocate the
controls to the subform which is where they now reside. Thank you so much
for patiently enduring these bits and pieces postings. Part of my inquries
have been taking place at home when I have no direct access to the database
and I foolishly try to communicate from memory. But here at work today, in
front of the database, I confirm that you have the most up-to-date info.

Sorry to be so thick about this:
FrameDaysAhead is on the main form; I presume that DateHolder1 and
DateHolder2 are also on the main form?
But the query uses a parameter of
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder1]
which is looking for the DateHolder1 control on the subform?

FrameDaysAhead is on the main form, which does its job, even when the
individual Analyst is filtered.

For instance, if Analyst "Smith" is the person of focus and has her 30 days
items showing, when I hit the 60 or 90 day radio button, the records change
accordingly. As well, when no one is filtered, the entire subform responds
with the desired date ranges.

All is well until the FilterBySelection is removed either by the built-in
Access toolbar RemoveFilterSort lightning bolt button or the double-click
Analyst field of the subform with the Me.Filter = "" code. Same zero
response result until the hidden binding is flushed when the entire
Workstation1 form is closed and reopened.

Is FrameDaysAhead on the main form, or the subform?

Private Sub FrameDaysAhead_Click()
Select Case FrameDaysAhead.Value
Case 1
[DayHolder1] = Now()
[DayHolder2] = Now() + 30
Me.Requery
Case 2
[DayHolder1] = Now()
[DayHolder2] = Now() + 60
Me.Requery
Case 3
[DayHolder1] = Now()
[DayHolder2] = Now() + 90
Me.Requery
End Select
End Sub

:

What is the code which runs when you click an option button in
FrameDaysAhead?

Private Sub Analyst_Click()
RunCommand acCmdFilterBySelection

Private Sub Analyst_DblClick(Cancel As Integer)
Me.Filter = ""

On the Double-Click I've also used RunCommand acCmdRemoveFilterSort.
Both Click and Double-Click functions seem to work perfectly. I've
used
Me.Requery in the Double-Click code after the sort as well. The
filtering
and unfiltering processes appear to be working fine.

It's the FrameDaysAhead requerying that seems to take a coffee break
after
the filter removal until I close the main form and reopen it again.


:

Could you post the code for the single- and double-click events for
the
Analyst control?

Yes. After a successful date range filtering using one of the
radio
buttons,
(30 days from Now() to Now()+30 being the default), a user can
then
single-click inside the Analyst field to select a specific
analyst,
then
successfully click another radio button within the DaysAhead
option
frame
to
view 30, 60 or 90 days ahead for that analyst. All is well until
they
double-click the Analyst field to RemoveFilterSort, which works,
but
for
some
reason the radio button is rendered "dead" at that point. No
error or
anything except a "calculating" indicator down at the bottom left
of
the
window, resulting in no further filtering. Only when the form is
reopened
will the original filter be enabled again. This is on a tab
control
page
as a
subform called frmSubfrmExpirations30 bound to qryExpirations
query
where
the
query date has the parameter Between
Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder1]
and

Forms![frmWorkstation1]![frmSbfrmExpirations30].Form![DateHolder2].

I've tried placing the Option Group and the DateHolder1 and
DateHolder2
fields on the main form as well as the subform but end up with the
same
results.


:

Could you be more specific about "quit working"?

I don't have the database available at the moment for all
specifics,
but
my
general question is, why would an option group frame named
DaysAhead
(3
radio
buttons 1 = 30, 2 = 60, 3 = 90 (days) )work perfectly to
regulate
displayed
date ranges on a continuous form but quit working when any
data
field
is
FilterBySelection then restored to full view through
RemoveFilterSort?
This
is on an Access2002 dbase.
The DaysAhead frame is used to fill two date fields: Date1
and
Date2.
Date1 is always Now() and Date2 is Now() + DaysAhead.Value
(30, 60
or
90).
Date1 and Date2 are the date criteria on the Expiration form's
qryExpiration
query, which are requried in the AfterUpdate Event of the
DaysAhead.