K
kev100 via AccessMonster.com
** REPOST OF AN OLDER UNFINISHED THREAD **
I agree as well, in most cases, however, in this particular application the
"names" will actually be unique numbers between 1 and 3 digits long. A pull-
down option would end up being just a giant list, hundreds of numbers long.
Here's the SQL view of that query.
SELECT results.route
FROM results
WHERE (((results.route)=[Route:]))
ORDER BY results.route;
The table name is "results"
The field that is being querried on is "route"
Currently, the user is prompted to enter the Route name (which is actually a
number) they want to see all records for. However, they can only enter 1
route at a time.
They need to be able to enter 1 or More routes and have the query show all
entered. Seperating each by a comma will not be a problem. Since route
"names" are actually numbers, the chance of entry errors will hopefully be
reduced..
Thanks
[quoted text clipped - 3 lines]The user running the query will be prompted for first names. They must be
entered exactly as stored in the first name field and must have a comma
frustrations. I would create a form with a multi-select list box as
suggested by Tom Ellison very early in this thread.
I agree as well, in most cases, however, in this particular application the
"names" will actually be unique numbers between 1 and 3 digits long. A pull-
down option would end up being just a giant list, hundreds of numbers long.
Here's the SQL view of that query.
SELECT results.route
FROM results
WHERE (((results.route)=[Route:]))
ORDER BY results.route;
The table name is "results"
The field that is being querried on is "route"
Currently, the user is prompted to enter the Route name (which is actually a
number) they want to see all records for. However, they can only enter 1
route at a time.
They need to be able to enter 1 or More routes and have the query show all
entered. Seperating each by a comma will not be a problem. Since route
"names" are actually numbers, the chance of entry errors will hopefully be
reduced..
Thanks