Form Filtering

[David Jay]

I have a database of customers, each assigned a route number, (1-10). When I
need to print a route, i filter the database by route number, sort by
sequence, and print. Most of my customers need deliveries each delivery day,
but some of my customers however, would prefer to have a delivery once every
OTHER route day, so while I print the route, a delivery slip is printed for
all customers in that route, even though some only need to be printed every
other time. This is a waste of paper, ink, etc.

Does anybody know how I can assign the customer route numbers, or a
different filter system that can filter all customers one day, and all but
some the next?

TIA,

Dave.

 

[Ken Snell [MVP]]

Sounds as if you need another field in your table that identifies the
"delivery frequency". Then you could filter based on that field, if you can
always identify when it's a "all" day and when it's a "every other day".

Note that you need to be clear in your definition of how *you* know which
customers are to be selected each day and which ones aren't before you can
tell your database how to make that decision for you.

 

[David Jay]

So... if i have route 1(a) and 1(b), i should create another field for this
a,b value? Then if I filter to route 1, then filter again to "a" or "b"
customers? That is actually fairly simple when you think about it. I thought
there might be a way i could label the routes 1A and 1B in the same field,
but I guess that's not possible.

Thanks Ken!

Dave.

 

[Ken Snell [MVP]]

It's possible to put 1A and 1B in the same field, but it makes it difficult
to parse the data back into its separate pieces. A relational database
should store atomic data (divided data, not combined data), as you can
always use queries and expressions to display combinations of separate
fields at any time, while retaining the easy ability to filter on the
separate fields.