Re: Delivery Addresses
- From: Tim Ferguson <FergusonTG@xxxxxxxxxxxx>
- Date: Thu, 06 Apr 2006 08:39:53 -0700
=?Utf-8?B?RGF2aWQgTSBD?= <DavidMC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
news:09C14525-086F-466C-9F87-C3DA97AB55A4@xxxxxxxxxxxxx:
Trouble with top-posting is that it's never completely clear what bits of
a reply correspond to which bits of a post. If I have misunderstood,
please correct me:-
4) Display the actual address lines in the combo box. Allow the user
to filter the combo box so that it only displays addresses that are
applicable to the current customer.
I'm not sure how this would help with inputting new addresses.
This was in your OP:
they have to open another form, enter the new delivery
address, give it a memorable reference so it can be
easily identified in the combobox, close that form,
then select the new delivery address from the combobox.
so if the users can see the actual addresses in the combo then they don't
have to remember anything.
With a bit of imagination and creative coding, it's possible to
create a fuzzy look up and try to identify the user's "21 St John
Ave" with the record in the database "21 Saint John's Avenue" but
it's not always easy!
When I say "save/load addresses" I mean that common addresses will be
stored in a seperate table still, but will be selectable from a popup
and copied to the Order table.
Okay -- I was imagining a proper related Addresses table. If you have a
simple copy-and-paste source table then life for the developer becomes
much easier. Separate form for maintaining the addresses table is
probably the way to go then.
B Wishes
Tim F
.
- References:
- Re: Delivery Addresses
- From: Tim Ferguson
- Re: Delivery Addresses
- Prev by Date: RE: Where to add these extra fields?
- Next by Date: Re: relationship to the same table
- Previous by thread: Re: Delivery Addresses
- Next by thread: Re: Delivery Addresses
- Index(es):
Relevant Pages
|