Before i throw myself into Access, a small question....

T

Thai

Hi all,
We need a database that will contain product numbers combines with serial
numbers but...
we handle parts for diverse companies and a lot of the product numbers are
common numbers and it also happens that serial numbers are equal.

The question is,
should we create "double" lists i.e. "compAproduct" "compBproduct" together
with "compAserial" compBserial" etc and if so, is it possible to get a
report with all productnumbers of all companies with the corresponding
serial numbers?
Or is it some kind of impossibility.
Till now we have everything on paper sheets, the old fashioned way.

Thanks in advance and Greetz,
Ron
 
E

Ed Robichaud

One main table will do, though you'll need to create your own unique ID for
each item - autonumber works well here. For each unique part, enter (accept
the generated) ID#, then enter company, PN and SN. This will accommodate
similar/overlapping pn/sn's, but there will be only one unique combination
of company, pn and sn.
-Ed
 
P

PC Datasheet

I know that and provide a lot of free support in the Access newsgroups!

Your name is never seen as a Access support provider!

BTW, what happened to your
John... Visio MVP

--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
[email protected]
www.pcdatasheet.com
 
M

Maha Arupputhan Pappan

Hi Ron,

I agree with Ed. I table is enough to manage your information for each
product. Set the Product Number field as the Primary Key.

Good Luck.
 
K

Keith

Apparently you still have NOT learned.

If anything, it's even more blatant than ever.
 
J

John Marshall, MVP

PC Datasheet said:
I know that and provide a lot of free support in the Access newsgroups!
Click to expand...

True, but that is not the issue you are being taken to task on. It is your
offering to help without disclosing the cost. These newsgroups are provided
for free support, so any offer to help has an implied meaning that it is
also for free.
Your name is never seen as a Access support provider!
Click to expand...

Does that make a difference? I am an Access user, so visiting this newsgroup
is useful. In the past I have answered (and asked) questions in this
newsgroup, but the regulars tend to be quicker on the response key.
BTW, what happened to your
John... Visio MVP
Click to expand...

Though I have recieved MVP awards for another Office product for many years,
the presence or absence of the MVP tag should not make a difference to the
viability of my original comment.


John... Visio MVP
 
M

MacDermott

Ed and Maha are correct that one table is the best way to organize this.
If you want to make sure that each company can have only one instance of any
product number, you can create a unique index using these two fields.
This can also serve as your primary key; there isn't any real need for an
additional (autonumber) field, although you may find it convenient to have
one.
 
Top