By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,573 Members | 938 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,573 IT Pros & Developers. It's quick & easy.

Remove Filter/Sort Does Weird Thing With Sub Forms

P: n/a
The following is happening in two instances in A2003. The one I
s\describe is the easiest one. Theme controls and autocorrupt have been
turned off long ago.

An unbound main form with a list box (query row source and multi-select
turned off) and a datasheet subform. The short cut menu for the
datasheet subform includes standard sort ascending and descending and
remove filter/sort menu items. The recordsource for the subform
datasheet is a parameter query where the vaue of the list box makes the
where clause. After update for the list box requireis the subform.

With the above arrangement, the records displayed in the subform change
every time a different row in the list box is selected.

Whenever the subform is sorted and then the remove filter/sort menu item
is selected, the results on the subform no longer change when a
different row is selected in the list box. When the main form is closed
and then opened again, it behaves as expected.

What might be causing the subform to "freeze"?
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Tim, I think you are describing a known bug in Access.

See:
Incorrect filtering of forms and reports
at:
http://members.iinet.net.au/~allenbrowne/bug-02.html

The list is not exhaustive, but it does outline some of the bugs associated
with filters that have been present for the last 5 VERSIONS of Access, i.e.
for 9 YEARS, and Microsoft still has not fixed them. It *really* annoys me
that they just keep releasing new versions with the same known bugs.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Tim Marshall" <TI****@antarctic.flowerpots> wrote in message
news:cs**********@coranto.ucs.mun.ca...
The following is happening in two instances in A2003. The one I
s\describe is the easiest one. Theme controls and autocorrupt have been
turned off long ago.

An unbound main form with a list box (query row source and multi-select
turned off) and a datasheet subform. The short cut menu for the datasheet
subform includes standard sort ascending and descending and remove
filter/sort menu items. The recordsource for the subform datasheet is a
parameter query where the vaue of the list box makes the where clause.
After update for the list box requireis the subform.

With the above arrangement, the records displayed in the subform change
every time a different row in the list box is selected.

Whenever the subform is sorted and then the remove filter/sort menu item
is selected, the results on the subform no longer change when a different
row is selected in the list box. When the main form is closed and then
opened again, it behaves as expected.

What might be causing the subform to "freeze"?
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto

Nov 13 '05 #2

P: n/a
Allen Browne wrote:
Tim, I think you are describing a known bug in Access.

See:
Incorrect filtering of forms and reports
at:
http://members.iinet.net.au/~allenbrowne/bug-02.html


It does indeed look that way, thanks. I ended up having to write a
function for each "remove filter/sort":

function fRemoveSortDataSheet(frm1 as form)

dim strS as string

strS = frm1.recordsource

frm1.recordsource = strS

end function

Does the job!

Thanks (again!) Allen.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto
Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.