Hey,

I have to store all the hardware in a network in an access db... I have made
some tables like servers, pc's, hubs, printers, ... But I now have to draw
the relationships between them...

A printer can be installed on more than 1 pc, more than 1 printers can be
installed on 1 pc ==> n on n relationship

More than 1 pc's can be installed on 1 hub, but can there be more than 1
hubs on 1 pc?

I don't know that much about networks, so I could use some help... Could
anyone give me some more insight on all the possible relations between these
items?

Thanks

A printer can be installed on more than 1 pc, more than 1 printers can be
You would need to break this into 2 one to many relationships by having a
printer table and a pc table and the a printerpc table with only the keys
from both pc and printers tables. the printerpc acts as a bridge table to
elimnate your many to many relationship and changes it into 2 one to many
relationships.

Same theory applies here as one PC could have 2 network cards plugged into
different hubs, if you still cant get it i can upload a mdb example, are you
doing this in access or sql?




"Oswald" <fluffster71 (AT) hotmail (DOT) com> wrote

In Access... the problem is that I don't really know what a network looks
like... I have an idea, but I don't know all the details...

For instance: a printer can be fysically connected with one pc, but can be
installed on many pc's... how could I store this? The goal is to know what
pc's have to be reconfigured if something happens to the printer (like
driver update) and to know where the printer is fysically (like when the
cable fails and needs to be replaced)

Any help would be welcome...

It's the analysis of the network that's troubling me... the entity
relationship diagram...

Thanks for your help so far...




"Jeff Brown" <notgiven (AT) thistime (DOT) com> wrote

The way I would do this would be to create a table for the PC's and
this table would have a primary key (Example PCID). I would then
create a second table for the printer information, This table would
have a column called PrntID along with what ever other information you
want about the specific printer (Example: Networked, Shared, Direct
Connect, Manufacture, Model, IP Address, etc). You DO NOT want to put
any PC information in this table.

I would then create a main form for bound to the PC Table, and a
subform bound to the Printer Table. Insert the Subform in the main
form. The master link would be the PCID, and the chile link would be
the PrntID. Make the subform a continous form so you can add as many
printers to each PC as you wish.

You then will be able to create queries that can search by PC and tell
you all the printers attached to that pc and how they are attached
(Networked, Shared, or Direct Connection). You'd have a one to many
between the PC Table and the Printer Table linked by PCID and PrntID.
You can also create a query for a specific Printer and show all the PC
that are connected to that printer. This would be a one to many
between the Printer Table and PC Table linked by PrntID and PCID.

Hope that helps....

Del

On Tue, 16 Sep 2003 09:54:11 GMT, "Jeff Brown" <notgiven (AT) thistime (DOT) com>
wrote:

Hey,

thanks, that really helps!

But what is a continous form?


"Del" <dtlabo (AT) yahoo (DOT) com> wrote

Oooooooooooops.... Should be "Continuous Forms", the spell checker
doesn't work on the free version of this news reader...... ;-)

Anyway let me know if you need any more help with this. If you like I
can send you a sample of what I'm talking about.


On Wed, 17 Sep 2003 09:17:46 +0200, "Oswald" <fluffster71 (AT) hotmail (DOT) com>
wrote:

Hehehee... I thought you meant to say continuous, but I still don't know
what that means...

An example would be nice!

Thanks everyone for the help so far...


"Del" <dtlabo (AT) yahoo (DOT) com> wrote