B
Bill
I need to implement the equivelent of how Windows
Explorer handles multiple selects, (which is also how
most list oriented Windows applications work). That
is, the user holds down the Ctrl key and selects one
row at a time to essentially build a collection of
whatever is being displayed with each remaining
highlighted as he/she progresses. Then, right-clicks
anywhere within the highlighted items and chooses
the function desired for the collection via a shortcut
menu.
The first approach that comes to mind, is to insert
each selection into what would become the equivelent
of a query that has a "list" of record ID's as its
"selection criteria". That way, the query is simply
the recordsource for whatever function is choosen
by the user. E.g., SELECT from "name of current
form's Recordsource" blah blah blah WHERE
RecordID = (ID1, ID2, ID3, ID4.....IDn). I'm a bit
rusty on how to build the SELECT in code, but I can
probably fumble my way through that, having work
I did a year ago as my guide.
Once again, if what I've described above is what
would be considered a preferred approach, I need
to learn how to:
1) Retain highlighting for each record selected.
2) How to sense if the Crtl key is depressed so as to
trigger insertion of the RecordID into the WHERE
clause of the SQL SELECT described above.
3) Revert highlighting from item 1) above.
4) Given it's possible, how to build the WHERE clause
for the SQL SELECT.
5) Make the temporary recordset created by the query
visable to code outside of the forms codesheet.
I'll stop with the questions here until my approach is
deemed appropriate by reader(s) of this post. I'll try
to stay out of trouble while I await a reply... hahaha!
As always, thanks and blessings to you all.
Bill
Explorer handles multiple selects, (which is also how
most list oriented Windows applications work). That
is, the user holds down the Ctrl key and selects one
row at a time to essentially build a collection of
whatever is being displayed with each remaining
highlighted as he/she progresses. Then, right-clicks
anywhere within the highlighted items and chooses
the function desired for the collection via a shortcut
menu.
The first approach that comes to mind, is to insert
each selection into what would become the equivelent
of a query that has a "list" of record ID's as its
"selection criteria". That way, the query is simply
the recordsource for whatever function is choosen
by the user. E.g., SELECT from "name of current
form's Recordsource" blah blah blah WHERE
RecordID = (ID1, ID2, ID3, ID4.....IDn). I'm a bit
rusty on how to build the SELECT in code, but I can
probably fumble my way through that, having work
I did a year ago as my guide.
Once again, if what I've described above is what
would be considered a preferred approach, I need
to learn how to:
1) Retain highlighting for each record selected.
2) How to sense if the Crtl key is depressed so as to
trigger insertion of the RecordID into the WHERE
clause of the SQL SELECT described above.
3) Revert highlighting from item 1) above.
4) Given it's possible, how to build the WHERE clause
for the SQL SELECT.
5) Make the temporary recordset created by the query
visable to code outside of the forms codesheet.
I'll stop with the questions here until my approach is
deemed appropriate by reader(s) of this post. I'll try
to stay out of trouble while I await a reply... hahaha!
As always, thanks and blessings to you all.
Bill