Relationship not in relationship window - I can't update table

[AMLR]

I am a novice regarding Access...
I have created a database with a form and a report.
The main database pulls information from a number of mini-tables.

I've realized that some of the table's fields have to be increased in size -
but each time I try to modify the various fields... I get a message that I
must remove the relationships and that I can view the relationships in the
"Relationship Window"... That's all well and good - but when I go into the
Relationship window - nothing shows up. I've pressed show direct and show
all... and nothing comes up... How do I remove the blasted relationships so
that I can increase the size of the fields... I have too much information in
each table to have to delete them and recreate them just to increase a field
from 50 to 150 characters!

Can anyone help me? I'm incredibly frustrated and need to get this up and
running very soon...

Thanks, Angie

 

[Jeff Boyce]

Any chance you've used the "lookup" data type in defining your tables (I
can't tell if this is what you are referring to with "mini-tables")? A scan
through this (tablesdbdesign) newsgroup will reveal a STRONG consensus
against using lookup data types in table definitions.

Among the many reasons not to I believe you will find that Access has
established a relationship "behind the curtain" on your behalf, and out of
your control.

Or am I barking at the wrong car?

Jeff Boyce
<Access MVP>

 

[AMLR]

Hi Jeff...
Thank you SO MUCH for your response... I really needed help...
Yes, I did use the look-up wizard and then selected the first choice, which
was "I want the lookup column to look up the values in a table or query"...
then I pointed to the table I wanted to reference... and that was that.

So... in my desperation, I've decided to just trash the database - which has
very little data in it anyway... and just re-create one. That being said...
could you recommend the best way to begin? Since, using the lookup wizard
was hazardous to my mental well-being?

Cheers, Angie

 

[Jeff Boyce]

Angie

There's nothing wrong with looking up, but given the current tool set, you
are probably better off doing your looking up in forms, not in tables
('tables store data, forms display it').

And you would not need to trash your db if you go through your current
tables (with lookup data types) and change the data type to "match" the data
type of the key of the "looked up" data/table. For instance, if you have a
looked up table with an autonumber primary key, your table definition in
your "main" table would need to be changed from "look up" to Long Integer
(so as to "match").

If you use a combo box in your form, you can specify the row source as your
lookup table or a query thereon (and if you use 0 as the width of the key
field, the combo will display the next, hopefully more meaningful field).
By setting the control source to the "main" table's field, you get to look
up (on the form) by a meaningful value, and store (in the main table) the
underlying key.