double database inrelationships?

[hermie]

Hello I have a database for schoolstudents which is replicated. Now I see in
my relationships a table 2 times eg Students and Students_1.
Students is an excisting table but students_1 is not.
When I delete students_1 and save the relationships It comes back again when
I open the relationsship again.
Is this normal? What can be wrong?

Herman

 

[John Vinson]

Hello I have a database for schoolstudents which is replicated. Now I see in
my relationships a table 2 times eg Students and Students_1.
Students is an excisting table but students_1 is not.
When I delete students_1 and save the relationships It comes back again when
I open the relationsship again.
Is this normal? What can be wrong?

Herman

It's not really a second *table* - it's just a second icon displayed
on the relationships window. This happens if you have two different
relationships established between a pair of tables, which can occur if
you are legitimately relating two tables in two different ways, or
because you've used Microsoft's obnoxious Lookup Wizard misfeature.
The latter creates additional relationships even if relationships
already exist.

Check each relatioship by clicking on the *join line* (not the table
icon) and viewing the join's properties. If there are two
relationships joining the same two tables on the same two fields, you
can safely delete one of the relationships. Again select the *line*,
not the icon, and use the Delete key on the keyboard.

John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps

 

[Christopher Glaeser]

It's not really a second *table* - it's just a second icon displayed

on the relationships window. This happens if you have two different
relationships established between a pair of tables, which can occur if
you are legitimately relating two tables in two different ways, or
because you've used Microsoft's obnoxious Lookup Wizard misfeature.
The latter creates additional relationships even if relationships
already exist.

Is there a way to avoid the Lookup Wizard? When I carefully place all my
tables and relationships for easy reading, then close and reopen the
relation window, Access redraws the diagram by introducing new dummy tables
and all the relations are overlapping spaghetti.

Best,
Christopher

 

[John Vinson]

Is there a way to avoid the Lookup Wizard? When I carefully place all my
tables and relationships for easy reading, then close and reopen the
relation window, Access redraws the diagram by introducing new dummy tables
and all the relations are overlapping spaghetti.

Sure, you can avoid the Lookup Wizard. JUST SAY NO!

Don't define any fields in your table as Lookup Fields. They are NOT
obligatory; they are NOT necessary; and they're NOT even helpful!

If you need a lookup capability - and, of course, you will - simply
create the lookup table yourself, just as a native table; for instance
you could have something as simple as

Titles
Title Text(15)

with values "Mr.","Mrs.","Ms.","Miss","Dr."

which would give you the flexibility to add

"His Excellency","Her Royal Highness"

when occasion arose. With this, you could use a Combo box bound to
Titles on a form to enter data into a text Title field.

Or, you could have a two-field lookup table:

Departments
DepartmentID Autonumber
Department Text

Put a Long Integer DepartmentID in your personnel table, and again use
a combo box on a Form based on Departments; the ID would be the bound
column but the department name would be the visible column.

The relationships window will *still* be flaky. I really like the
multiple adjustable relationship windows in a Microsoft Project .adp -
wish they could do the same with .mdb files!

John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps