Help!

[frank]

All

I want to create a simple database with three columns containing a name in
the 1st column, another name (related to the name in the 1st column) in the
2nd column and a name ID number (again related to the 1st column name) in
the 3rd column. Then, if this is possible, when I enter the name in the 1st
column, the related name and ID number are automatically filled in, in the
2nd and 3rd colums. The names and numbers would ideally be contained in a
combo box in each of their respective columns.
Can anyone point me in the right direction to achieve this or can't it be
done?

Thanks

Frank

 

[frank]

All

By the way, forgot to say I'm using Access 2000.

Frank

 

[John Vinson]

All

I want to create a simple database with three columns containing a name in
the 1st column, another name (related to the name in the 1st column) in the
2nd column and a name ID number (again related to the 1st column name) in
the 3rd column. Then, if this is possible, when I enter the name in the 1st
column, the related name and ID number are automatically filled in, in the
2nd and 3rd colums. The names and numbers would ideally be contained in a
combo box in each of their respective columns.
Can anyone point me in the right direction to achieve this or can't it be
done?

Sounds like you need a Query, not a table. Are the 2nd column names
drawn from the same set of names as those in the first column? If so
I'd suggest two tables:

Names
ID
NameField <don't use Name, it's a reserved word

Relationships
ID1
ID2

You can then create a Query joining Names to Relationships by joining
ID to ID1, and then joining that to another instance of Names joining
ID to ID2. Displaying this query as a datasheet or (better) on a form
or report will do the automatic linkage for you.

Suggestion: DON'T use combo boxes in tables... ever. They conceal the
actual content of the table, and do you *very* little good in exchange
for quite a bit of hassle.

 

[frank]

John

Thanks for your reply.

If tables are not the best with combos's, a form would be fine.

The names are completely different. The names are actually a bird name (ie.
'bird species'), its 'scientific name' (Latin of course) and a species ID
number, all related to each other. Ideally if I filled in any on of the
three the other two would fill in automatically but just filling in the name
of the 'bird species' would be fine as long as the other two associated
items filled also.

Hope this makes it clearer.

Frank

 

[John Vinson]

John

Thanks for your reply.

If tables are not the best with combos's, a form would be fine.

The names are completely different. The names are actually a bird name (ie.
'bird species'), its 'scientific name' (Latin of course) and a species ID
number, all related to each other. Ideally if I filled in any on of the
three the other two would fill in automatically but just filling in the name
of the 'bird species' would be fine as long as the other two associated
items filled also.

If you have the unique SpeciesID in your table, it's NOT necessary to
have _Falco peregrinus_ in the record in that table; having in the
Species table is sufficient. Storing it redundantly in a second table
is not necessary. You can *display* the other fields on the Form using
the combo box's Column property - set the control source of a textbox
to

=cboSpecies.Column(n)

where n is the zero based subscript of the field in the combo.