Database design

[LMichel]

Version en français ci-dessous

I want to make a database to handle CD-R that are used by our technicians to install PC.
What is a problem for me is that they are two kinds of CD-R.
First kind contains standard application like MS office, visio, ...
Other kind of CD contains images of hard disk made by Altiris express (disk imaging utility)
For standard application, all I need to know is manufacturer name, version
For Images, I need to know for which computer this image is made.

They are multiple copies of an application or image

My goal is to know which CD a tech own.

-----------------------------------------------------------

J'aimerais créer une base de données pour gérer les CD-R prêtés à nos techniciens.

La difficulté est qu'un CD peut contenir deux types de données différentes.
Le premier type est une application standard comme MSoffice, visio...
Le second type est une image réalisée par Altiris eXpress (image d'un disque dur)

Pour les applications standard, j'ai besoin de connaître le numéro de version et l'éditeur
Pour les images, je dois connaître le type de PC auquel l'image est destinée

Une image ou une application peut avoir plusieurs copies.

Le but est de déterminer quel technicien possède tel CD.

Ce que je n'arrive pas à exprimer dans mon design est qu'un CD peut avoir des types de contenu différents.

 

[MichaelRed]

In the simplest sense, creatge a table with fields:

[TechId] for the Technician
[AppCd] for the "applications" type of CD
[Cd-Key] Applications CD's often need a Key code to use.
[ImageCd] for the Machine/Image Cds. Enter the "MachineID" here
[CdDate] for the date/time of the 'Recording'

For the Applications CDs, the Image fields will be left blank, for the Image Cds, the Application Fields will be left blank.

This is not the "Best" aproach, but for a beginner it may be easier to deal with. Is shows - at a glance - which category the Cd is in.

Since (I assume) this is for a small to moderate company, the 'waste' of storage is inconsequential.

MichaelRed
mred@att.net

There is never time to do it right but there is always time to do it over

 

[LMichel]

Ok, I've tried your solution and It works fine !
Please, let me know what is the "best" aproach for you. I want to learn !
Thanks for your help.

 

[MichaelRed]

Hmmmmmmm,

Depending on your degree of 'beginnerness', this may be hard to understand?

One small step could still use a single table. It would have:

[TechId] 'Technicial Identifier
[CdId] 'CD Identifier (Serial Number?)
[CdType] '= [App | Image]
[CdDetail] 'If ([CdType] = "Image&quot then
' [MachineId]
' ElseIf ("HasKey&quot then
' [CdKey]
' Else
' Leave Blank
'End If
[RecDt] 'Record Date (Update when any info changed)


Annother Schema,

Two Tables.

[tblTech]
[TechId]
[CdId] 'Primary Key
[RecDt]

tblCd
[CdId] 'Foregin Key
[CdType] '=["App" | "Image"]
[CdDetail] 'As Above
[RecDt]

The latter offers the opportunity to work with the relational aspects of the database egine and a small additional 'flexability'. Again, for a small to medium size business, I do not believe there is any real need to do any more than the original posting.

MichaelRed
mred@att.net

There is never time to do it right but there is always time to do it over