converting text box to combo box and using linked data

  • Thread starter Thread starter Ted
  • Start date Start date
T

Ted

the ingredients of question come as follows:

i have two a2k databases. we'll call them 'A' and 'B'. 'A'
has been around for a long time and has lots of records.
'A' currently requires its user to input a field, call
it 'Title' as a text field.

the database 'B' is the newer of the pair and will be
having its user input info into a field called 'Title'.

the information in both 'Title' fields is intended to
capture the same informaiton.

it is the intent of the mgt to use the information from
the 'Title' field in 'B' to hereafter populate the 'Title'
field in 'A' (via a linking of the table in 'B' having
the 'Title' data).

i envisage converting the text field in 'A' to a combo box
whose Row Source is a query to the 'Title' field in the
linked table in 'B'.

the thing is that i'm concerned the underlying table
in 'A' will not be able to continue to use the information
in the title field that's already been entered.

is this a problem? will it matter to a2k once i convert
the text control on the 'A' form to a combo box.
..
 
Why are you duplicating data? Why not have a table of [name], [title], etc.
and link it to both A and B. That way you'll only be maintaining one set of
contacts/customers/members that can be linked and used by many other
databases.
-Ed
 
in case there was some 'terminological ambiguity' in my
posting, the older database ('A') has a table (and a form
over it) that has been around for dog's years (a really
long time) and the individual responsible for entering
data into it has amassed thousands of records' worth of
data (each one of which you'll recollect has had data
input into the 'Title' field).

the mgt have decided to develop another database (on the
same server) which will house (among others) a table that
will include a field for 'Title'). i think to make this
clearer, mgt have decided that the new 'B' database's
control holding 'Title' will serve as the source for the
old one's 'Title' control. to put this into a functional
framework, the user of 'A' will be entering the value
of 'Title' in its host table and the user of 'B' will have
that information available to him/her in their table in
the 'B' database holding that control. the idea is to
minimize the errorproness of entering data into
database 'A' via a combobox in 'B' which uses a query on
the 'Title' field in the table you find it in in the 'B'
database.

the question for me is, given that this paradigm will be
the way things get done here forward, what happens to the
pre-existing 'Title' data in their host table in the 'A'
database.
-----Original Message-----
Why are you duplicating data? Why not have a table of [name], [title], etc.
and link it to both A and B. That way you'll only be maintaining one set of
contacts/customers/members that can be linked and used by many other
databases.
-Ed

the ingredients of question come as follows:

i have two a2k databases. we'll call them 'A' and 'B'. 'A'
has been around for a long time and has lots of records.
'A' currently requires its user to input a field, call
it 'Title' as a text field.

the database 'B' is the newer of the pair and will be
having its user input info into a field called 'Title'.

the information in both 'Title' fields is intended to
capture the same informaiton.

it is the intent of the mgt to use the information from
the 'Title' field in 'B' to hereafter populate the 'Title'
field in 'A' (via a linking of the table in 'B' having
the 'Title' data).

i envisage converting the text field in 'A' to a combo box
whose Row Source is a query to the 'Title' field in the
linked table in 'B'.

the thing is that i'm concerned the underlying table
in 'A' will not be able to continue to use the information
in the title field that's already been entered.

is this a problem? will it matter to a2k once i convert
the text control on the 'A' form to a combo box.
.
Click to expand...


.
Click to expand...
 
Back
Top