Nick Nolte
|
| Posted: 06/11/2001, 1:29 PM |
|
In my application I've serveral forms which have many list boxes to look up
values from other tables (foreign keys). Some of this listboxes (employees,
departments, status, ....) are used very often. At the moment I must create
the list of values (LOV) as often as I need them. If the contents of a LOV
changes I have to change each LOV.
What I know from other development environments (especially Oracle) are
reusable shared components. One kind of such a components are LOVs. They
contain not much information, just the SQL Statement or a fixed list of
values pairs for storing and presentation.
CodeCharge support is thinking about a copy and paste facility for versionm
1.2, but that would not help much.
What do you think about the idea of shared components as LOVs (and fonts and
colors and help texts and ...)?
NIck
|
|
|
 |
Paul
|
| Posted: 06/11/2001, 1:40 PM |
|
In you database create a lookup table. Then use this table for your
listboxs. In the admin section of your application include pages for lookup
maintainence. If you need to make a change you go to admin menu select the
lookup table in question, make the changes and every place you use this
table in you app will reflect the changes you made.
Nick Nolte wrote in message <9g39ne$ipj$1@mail.tankhill.com>...
>In my application I've serveral forms which have many list boxes to look up
>values from other tables (foreign keys). Some of this listboxes (employees,
>departments, status, ....) are used very often. At the moment I must create
>the list of values (LOV) as often as I need them. If the contents of a LOV
>changes I have to change each LOV.
>What I know from other development environments (especially Oracle) are
>reusable shared components. One kind of such a components are LOVs. They
>contain not much information, just the SQL Statement or a fixed list of
>values pairs for storing and presentation.
>
>CodeCharge support is thinking about a copy and paste facility for versionm
>1.2, but that would not help much.
>
>What do you think about the idea of shared components as LOVs (and fonts
and
>colors and help texts and ...)?
>NIck
>
>
>
>
|
|
|
|
Nick Nolte
|
| Posted: 06/11/2001, 1:54 PM |
|
Paul, I'm not sure whether we are talking about the same thing. As far as I
understand you suppose to use a tables for the values of the LOVs, that is
one part of the problem. Therefore I want to reuse the SQL statement for
fetching the values from the lookup tables. But if I want to use the values
of one lookup table several times in my application I've to write the SQL
statement several times.
Think of an employee table as a lookup table. And now there a several forms
each containing a LOV for an emloyee: manager of a department, owner of a
pc, responsable for a task, leaning a book, ....
I want to store the SQL statement in only one place and use it in many forms
without making typos or using a different presentation of the list
(ordering, sequence of concatenated fields, ...)
"Paul" <paporter@visto.com> schrieb im Newsbeitrag
news:9g3aci$jbk$1@mail.tankhill.com...
> In you database create a lookup table. Then use this table for your
> listboxs. In the admin section of your application include pages for
lookup
> maintainence. If you need to make a change you go to admin menu select
the
> lookup table in question, make the changes and every place you use this
> table in you app will reflect the changes you made.
>
>
> Nick Nolte wrote in message <9g39ne$ipj$1@mail.tankhill.com>...
> >In my application I've serveral forms which have many list boxes to look
up
> >values from other tables (foreign keys). Some of this listboxes
(employees,
> >departments, status, ....) are used very often. At the moment I must
create
> >the list of values (LOV) as often as I need them. If the contents of a
LOV
> >changes I have to change each LOV.
> >What I know from other development environments (especially Oracle) are
> >reusable shared components. One kind of such a components are LOVs. They
> >contain not much information, just the SQL Statement or a fixed list of
> >values pairs for storing and presentation.
> >
> >CodeCharge support is thinking about a copy and paste facility for
versionm
> >1.2, but that would not help much.
> >
> >What do you think about the idea of shared components as LOVs (and fonts
> and
> >colors and help texts and ...)?
> >NIck
> >
> >
> >
> >
>
>
|
|
|
|
Henrik B. Rasmussen
|
| Posted: 06/11/2001, 4:18 PM |
|
"Nick Nolte" <nicknol@gmx.de> wrote in message
news:9g3b69$k89$1@mail.tankhill.com...
> Paul, I'm not sure whether we are talking about the same thing. As far as
I
> understand you suppose to use a tables for the values of the LOVs, that is
> one part of the problem. Therefore I want to reuse the SQL statement for
> fetching the values from the lookup tables. But if I want to use the
values
> of one lookup table several times in my application I've to write the SQL
> statement several times.
> Think of an employee table as a lookup table. And now there a several
forms
> each containing a LOV for an emloyee: manager of a department, owner of a
> pc, responsable for a task, leaning a book, ....
>
> I want to store the SQL statement in only one place and use it in many
forms
> without making typos or using a different presentation of the list
> (ordering, sequence of concatenated fields, ...)
Hi Nick,
Have you tried putting the SQL in a variable and use the variable as the SQL
in the CC-Forms?
/henrik
|
|
|
|
Nick Nolte
|
| Posted: 06/11/2001, 8:59 PM |
|
> Hi Nick,
>
> Have you tried putting the SQL in a variable and use the variable as the
SQL
> in the CC-Forms?
>
> /henrik
No, I haven't tried to put the SQL in a variable. That might be a step in
the right direction and I will get it a try. Possible problems could be
- naming of the variable is language dependant
- column(s) for presentation and storing have to be given each time the LOV
is used.
What do you think is the right place (form, include, ...) for those LOV
variables?
Thanks for the advice
Nick
|
|
|
|
|
