Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Creating Relationships on demand

Status
Not open for further replies.

OU18

Programmer
Aug 22, 2001
102
US
Hi All,

I am trying to create relationships between tables on demand. Meaning, user selected. I have been charged with building an Inventory Database for our network circuits (ie OC48,DS3,DS1,DS0). Under normal circumstances you couldnt have a DS3 without an OC level circuit. But at our company we do have inventory that does not have a higher level circuit.

I was going to build a table for each level.

tblOC48
tblDS3
tbDS1 etc...

Then when the user goes to enter new inventory, they open the appropriate form attached to that table and add the circuit being installed, while in the back ground the system auto links to the next table down.

So for example, our provisioners order a DS3. And also order the associated DS1's for that DS3. So they need to add the 28 T1's that go with it. So instead of going to the highest level (OC48) and entering all the way down through to the DS1 level, I would like there to be no relationships until the actual circuit level is selected and then have the system auto create the relationship to the needed table. In this case, from the tblDs3 to tblDS1.

Hope this makes sense and is possible. Or is there a better way to accomplish this task. Keep in mind there will also be situations where we start at the OC48 level and then Slot 48 DS3s to that OC48, and then slot the DS1's to each DS3.

Thanks everyone,.
 
Are you describing a 'Bill of Materials' situation? So I make a gizmo and need to add it to the inventory. In order to make a gizmo I need to use 15 widgets and 30 bolts. So I add a gizmo to inventory and subtract 15 widgets and 30 bolts.

Are you trying to do something similar? Where if you order a DS3, you also order a DS1 and a DS1 is made of up 28 T1's?

Leslie
 
Okay, let me see if i can explain this better.

Yes you are somewhat correct.

Not sure of your telecom knowledge, so I will go on the basis it is minimal.

OC48 = 48 DS3's
DS3= 28 DS1's
DS1 = 24 DS0
DS0 is the smallest circuit level availalbe.

In my situation, there are instances where we have an OC48 with available channels. (IE, 24 of 48 DS3's are capable of being used). In that case, if I was ordering a new DS3 and was using one of the available Channels, I would need to start at the OC48 level, and utilize slot 25 for my new DS3. Then I would order the 28 DS1's for that DS3.

But there are situations where we order a DS3 and it is not slotted against an OC48. In this case I would need to start at the DS3 level and then slot the DS1's. This situation sort of prohibits the ability to add the relationships at the table level. Instead I was thinking if I had someway to create the relationships on demand. Ie if i am on the DS3 form for entry, create the relationship to the DS1 table, for this particular instance.

Am I trying to do something completely idiotic. Is there a better way to do this.

And on a side note, do you play a lespaul. I am sure you have never been asked that question before. LOL

Thanks for the quick response.
 
OU18

Very complicated. I can use 12 of these ro 24 ofo those.

Consider this design...
I part of my in-house support database is to track IT inventory which includes PC's, printers, monitors, servers, switches, and peripherals - tape drives, CD-writers, docking stations.

Everything had to be tagged, and a requirement was that I could enter a tag number and pull up the information. Sounded simple until you realize that I had to be able to tell how big a hard drive a PC had, or the size of monitor, or the number of CSICO GBic fiber modules in a Catalyst 3550 switch.

This is a (hopefully) brief explaination...

DeviceMasterTbl
DevMID
DevType - type of device
TagNo
SerialNo
VenderID
Model
LocationID
OwnerID
ParentID
etc

DevPCTbl
DeviceID
DevMID - links to the device master table
Num_Drives
CPU
RAM
etc

DevPrinterTblD
DeviceID
DevMID - links to the device master table
PrinterType
PrinterSpeed
etc

DevSwitchTbl
DeviceID
DevMID - links to the device master table
Managed - T/F
NoPorts
etc

DevComModuleTbl
DeviceID
DevMID - links to the device master table
ModuleType
S/N
etc..

IPTbl
IPAddress
DevMID - links to the device master table


Okay, let's review.
The device master can have several components including multiple IP addresses (for servers, switches and routers).

I use the DevType to filter out what type of component devices to use. For example: ws-process and ws-office for process control and office workstations; prt-net and prt-loc for network and local printers. It gets interesting for the communciation equipment.

Next, I use a "parent ID". This gives me the ability, if required to tie a device to antoher. For example, a tape libary is tied to a server, or a monitor is tied to a workstation.

Note that for the communications, which is by far the most complex, several subcomponents can be tied to the device master.

Does this give you any ideas?

Richard


 
yes, i've been asked, but no I don't! I'm Leslie and my husband is Paul. Get it?

Hopefully Richard has been able to give you some ideas on how to handle your problem!

Les
 
Richard and Leslie,

Funny thing was after I posted this and went home. I started messing with it on my computer away from the office noise. It became very clear, when I started designing, and I actually came up with a very similar structure in my tables. I appreciate your posts.

Thanks again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top