Hi, Erick.
Any ideas or work arounds?
A guy has a car towed into an auto shop, and he tells the mechanic, "I want
you to make this car go faster." The mechanic lifts the hood to see what he
has to start with, but there's no engine.
"Where's the engine?" asks the mechanic.
"I don't have one, but I have some boat engine parts in a box in my garage
at home," says the customer.
"Do you want to purchase an engine and have me install it for you?" asks the
mechanic.
"An engine is irrelevant. I just need you to make this car go faster."
The analogy is that a box of engine parts is like a bunch of data dumped
into a table with no primary key. Until someone comes along with the skill
to organize the engine parts and build a working engine out of those parts
or to normalize the table with a primary key (which identifies individual
records and establishes relationships between records in other tables), it's
just a box of junk. The primary key is _that_ vital to having a table of
data: it's equivalent to the car's engine.
No engine, no faster car. No primary key, no table, no relationships.
Get a primary key on that table, and then you'll be able to work with the
data.
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog:
http://DataDevilDog.BlogSpot.com http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.
"erick-flores" <er**********@gmail.comwrote in message
news:11**********************@a75g2000cwd.googlegr oups.com...
>
Ok I think the problem is the link table does not has a pk. And of
course I cant set the pk because I cant make any changes to the link
table. That is why I can not create a one-to-one relationship and to be
able to enter the comments.
Any ideas or work arounds?