Duplicate Records in a form

[MJ]

I have created a table with Customer number as the key field and in
another table the key field is a combination of two fields: Customer
and System #. When I create a form I am getting duplicate listings for
the same customer. Any ideas of what I am doing wrong?

[Bob Quintal]

"MJ" <je*******@cox.net> wrote in
news:11**********************@g14g2000cwa.googlegr oups.com:

I have created a table with Customer number as the key field
and in another table the key field is a combination of two
fields: Customer and System #. When I create a form I am
getting duplicate listings for the same customer. Any ideas
of what I am doing wrong?

Two possibilities spring to mind. The first is that you have the
same customer listed twice, with different IDs. The other is you
have multiple system # entries against the same customer.

--
Bob Quintal

PA is y I've altered my email address.

[MJ]

Bob Quintal wrote:

"MJ" <je*******@cox.net> wrote in
news:11**********************@g14g2000cwa.googlegr oups.com:

I have created a table with Customer number as the key field
and in another table the key field is a combination of two
fields: Customer and System #. When I create a form I am
getting duplicate listings for the same customer. Any ideas
of what I am doing wrong?

Two possibilities spring to mind. The first is that you have the
same customer listed twice, with different IDs. The other is you
have multiple system # entries against the same customer.

--
Bob Quintal

PA is y I've altered my email address.

Yes, the second is correct. I have customers with more than one
system. I am a beginner in Access and am in awe of the questions
others pose on the Web sitr. I am strickly out of my league.

I do have customers with more than one system and am trying to figure
out how to set up the database so that I see a customer and all of
their systems (in a Form). Can't seem to be able to figure it out. A
little knowledge is dangerous!

[pietlinden]

Just a little piece of advice before you start building tables and find
out later that your design is wrong. Been there, done it. Not fun.
Fixing a bad design later is a HUGE headache. So it's best to "drink
deep" early.

You might want to read my instructor's "wee" introduction to data
modeling. Yes, it's perhaps on the long side, but you can learn by
reading or by trial and error... Here's the link:

http://www.cis.drexel.edu/faculty/so.../AppendixA.PDF

Yes, it's a bit heavy going, but if you understand and apply what he
says, you'll have a database that actually works. Otherwise, you'll
try and use it and find out you can't get answers out of it.

I know it's an indirect answer to your question but it's time well
spent - and it's only 20 pages... you could do much worse!

hope it helps.

[MJ]

pi********@hotmail.com wrote:

Just a little piece of advice before you start building tables and find out later that your design is wrong. Been there, done it. Not fun.
Fixing a bad design later is a HUGE headache. So it's best to "drink
deep" early.

You might want to read my instructor's "wee" introduction to data
modeling. Yes, it's perhaps on the long side, but you can learn by
reading or by trial and error... Here's the link:

http://www.cis.drexel.edu/faculty/so.../AppendixA.PDF

Yes, it's a bit heavy going, but if you understand and apply what he
says, you'll have a database that actually works. Otherwise, you'll
try and use it and find out you can't get answers out of it.

I know it's an indirect answer to your question but it's time well
spent - and it's only 20 pages... you could do much worse!

hope it helps.

[MJ]

Thanks! I will read it and hopefully it will resolve my issue.