Re: DropDownList

new topic     » goto parent     » topic index » view thread      » older message » newer message

Well, I guess it's because, it takes up too much space on the screen and on
some reports there's not enough room to print it and it's their own codes so
the're used to them and if the're not they need to get used to them, because
they show up on most internal documents...

This is just some design stuff that is well established and been around for
a long time..

...george
----- Original Message -----
From: "Irv Mullins" <irvm at ellijay.com>
To: "EUforum" <EUforum at topica.com>
Sent: Thursday, August 16, 2001 5:57 PM
Subject: Re: DropDownList


> >
> On Thursday 16 August 2001 16:59, George Walters wrote:
> >
> > Your program snipit looks like it would work fine if the dropdownlist
field
> > width could be larger than the coded field width. Can't see how to do
> > this.. The code in the field would be like 'n30' or 'n60' , so the
editText
> > field only should be 3-6 chars but the descriptive text for this could
be
> > much larger (usually about 15). The short code would be used in the DB
and
> > on internal reports, the long on invoices, statements, etc.
>
> Why not just leave the descriptive text in the dropdown?
> If a person chooses "2% 10, Net 30", then that will stay on the screen,
> but your db could store a code, say: 3,  in the terms column.
>
> When you later print reports, etc, you can expand that 3 to read anything
> you want -  "10n30", or "2% discount if paid within ten working
> days, net 30 days from date of invoice".
>
> Regards,
> Irv
>
> >
> >
>
>

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu