 | |
Autoupdateble Drop-down
comp.databases.filemaker comp.databases.filemaker
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Autoupdateble Drop-down -
01-12-2010
, 12:37 PM
#2
| |||
| |||
|
|
In this DB i have a feld "Person" as a dropdown in the tabel "Arkiv" This dropdown gets the information from the field "Name" in the tabel "Person" |
to give every record a unique number.
Quote:
|
When I edit a name in "Person" tabel, it dont update the "person" filed in "Arkiv" tabel. |
of the person.
Create a relation between the two tables: Person::__kp_PersonID =
Arkiv::_kf_PersonID
Display the related field Person::Name on the Arkiv layout.
Now the name of the person is stored in one place only. As soon as the
name changes, you will see it on the layout.
--
http://clk.ch
#3
| |||
| |||
|
|
HB Nielsen <h.b.n (AT) mail (DOT) dk> wrote: In this DB i have a feld "Person" as a dropdown in the tabel "Arkiv" This dropdown gets the information from the field "Name" in the tabel "Person" Create a number field __kp_PersonID in the person table. Use auto-enter to give every record a unique number. When I edit a name in "Person" tabel, it dont update the "person" filed in "Arkiv" tabel. In the Arkiv table, create a number field _kf_PersonID to store the key of the person. Create a relation between the two tables: Person::__kp_PersonID = Arkiv::_kf_PersonID Display the related field Person::Name on the Arkiv layout. Now the name of the person is stored in one place only. As soon as the name changes, you will see it on the layout. -- http://clk.ch |
#4
| |||
| |||
|
|
Will this also change already slected names, or only future entries? |
This data is independent from the data in your person table, so it
won't update.
I suggest you give each name in the person table a unique serial number,
create a field in the Arkiv table for this serial number and assign the
relevant serial number to each existing entry. In short: re-do the whole
thing. Then you won't need the existing name fields in the arkiv table,
you just put the related name field from the person table on the layout.
And these will, of course, always update, because it's the original
field itself.
--
http://clk.ch
#5
| |||
| |||
|
|
HB Nielsen <h.b.n (AT) mail (DOT) dk> wrote: Will this also change already slected names, or only future entries? I assume already selected names are in data fields in your Arkiv table. This data is independent from the data in your person table, so it won't update. I suggest you give each name in the person table a unique serial number, create a field in the Arkiv table for this serial number and assign the relevant serial number to each existing entry. In short: re-do the whole thing. Then you won't need the existing name fields in the arkiv table, you just put the related name field from the person table on the layout. And these will, of course, always update, because it's the original field itself. -- http://clk.ch |
#6
| |||
| |||
|
|
HB Nielsen <h.b.n (AT) mail (DOT) dk> wrote: Will this also change already slected names, or only future entries? I assume already selected names are in data fields in your Arkiv table. This data is independent from the data in your person table, so it won't update. I suggest you give each name in the person table a unique serial number, create a field in the Arkiv table for this serial number and assign the relevant serial number to each existing entry. In short: re-do the whole thing. Then you won't need the existing name fields in the arkiv table, you just put the related name field from the person table on the layout. And these will, of course, always update, because it's the original field itself. -- http://clk.ch |
#7
| |||
| |||
|
|
Do you mean that I must enter the serial number for each person instead of selecting the name in a dropdown list? |
and the name as a second field, have it sorted by the second field and
choose to display the second field only, you get the same experience:
you choose the name, but what gets entered into the field is the serial
number.
--
http://clk.ch
#8
| |||
| |||
|
|
or is it possible to create "update" script that can update i field?? |
every record, a value that can never ever be changed, you will regret it
sooner or later. You can not build the relation on the names because, as
it appers, they appear to change, and more important, because names are
not unique.
Quote:
|
I have 22 dropdown that gets data from the table "person" that need to be updated when a name i changed. |
related fields, showing the data of your person table, and therefore
always be updated. Build a proper relation based on a serial number, and
your problems are solved.
--
http://clk.ch
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.