Review my DB

[Acidburn]

tell me what you think

Tell me what you think!

http://www.zatrixsolutions.com/ex/database.zip
its not complete but comments welcome!

 

[Jack Cowley]

I do not like forms that open with a dialog asking for information. A misspelling can have you looking at a blank form. Allow the user to make a selection from a combo box or list box instead and open the form based on their selection. No possible errors using this method...

That is my 2 cents worth.

Jack

 

[Parker]

I agree with Jack

Not only will you have problems wiv shpelling but also cASe sens. format, etc

Beter to pick than ask for imput

End users are so unreliable

 

[a.sinatra]

What about a better look to the switchboard?

Lemme know what you think, see attached.
________
Ford Motor Credit Company

 

[wizcow]

Thumbs up on the new swtichboard look.
Nice logo too.

In your tables I see 'computanet' entered many times.
Consider making another table to hold PC brands, Monitor brands etc.
Then relate the brand to your first table.

Good Luck

Tom

 

[a.sinatra]

Thumbs up on the new swtichboard look.
Nice logo too.

Hrm. Maybe i should of worded my post better, the SS was nearly a suggestion. I am not the creator of the db
________
FORD 999 SPECIFICATIONS

 

[Acidburn]

no worries i like the new switch screen and I'll try and do what you said about the computer make ...

 

[Mile-O]

Re: tell me what you think

Tell me what you think!

It could do with normalisation before you even think of moving on and designing queries, forms, reports, etc. There are repeating groups and not enough tables to represent the data contained within.

The default Access "themes" are typically horrible and you'd be best advised to come up with your own.

Asking for parameters can generate numerous errors, empty queries, etc. and cannot be controlled with error handling.

 

[Acidburn]

Thanks for your comment. I'm going to review my tables, yet you talk about repeating groups of data? Thats due to the pc make itsself. What do you recommend? I have through about doing it the same way as my Location table? Is that table ok btw?

Also another query trying to make a combo box enter text in the text box when the user searches but when i chose the location from the combo list in the text box its enteres the ID not the location value any ideas?

 

[Mile-O]

I'm going to review my tables, yet you talk about repeating groups of data? Thats due to the pc make itsself. What do you recommend? I have through about doing it the same way as my Location table? Is that table ok btw?

No, it's not due to the PC make itself.
The table MonitorSpec's field (MonitorMake) should be a lookup field in another table.
I can't figure out what tblAssetNumbers is supossed to be.
The repeating group is in the table PCSpec. The repeating group is this: CPU Speed, Memory, HardDrive, NetworkCard, SoundCard, and Graphics.

This group should form a new table (tblComponents) with the structure:

tblComponents
ComponentID
Component

This way the table grows downwards.

Now, a second table (for cascading):

tblComponentTypes
ComponentTypeID
ComponentType
ComponentID - foreign key to tblComponents

You also need a table for PC Builds. (and not Spec)
This table should have the structure

tblComputersToComponentTypes
PCID
ComponentTypeID

Both these fields are used to make the primary key. They are both, also, foreign keys to the table: tblComputers, and the table: tblComponentTypes.

One more table: tblComputers.

tblComputers
ComputerID
ComputerModel
MonitorID - foreign key to monitors table
LocationID - foreign key to locations table

The reason for all of this? You have a many-to-many relationship and need to simulate this. By working with this normalised structure you ensure that you don't need to amend forms, queries, reports, code, etc. in the future.

Need a new component? Got to add types of mice or keyboards? Then all you do is define the new component in tblCompoinents and add each brand/model to tblComponentTypes. There's no need then to add a new field into the table PCSPec called MOUSE or KEYBOARD and then there's also no need to rebuild queries and forms to take into account the new components.

Also another query trying to make a combo box enter text in the text box when the user searches but when i chose the location from the combo list in the text box its enteres the ID not the location value

You need to set the ColumnCount of the combobox to 2. Set the ColumnWidth to 0.

 

[Acidburn]

Thanks again for the reply. However the whole point of this project was to STORE information about indivaual nodes. each node has been assigned an ID ( hint the autonumber) After this when the appropiate key is entered the information about the pc is the retived monitor make pc make etc etc. If this makes sence.

Also that combo box works has it bring up the names of the location eg MM however the ID is compied into the text box fields which i would prefere to hide the text box and copy the data to it. Eg the MM is copied and records are shown but you cant see the text box. . . with me?

 

[Mile-O]

the whole point of this project was to STORE information about indivaual nodes.

And the whole idea of normalising your database is to ensure the best possible design for both storing and retrieving data.

In the example you posted I saw nothing for storing information - it was ALL retrieval.

 

[Acidburn]

ar! sorry I'm new to the Access thing. Perhaps you could show me a working prototype of what you mean. As I still dont get ya!

 

[Mile-O]

Perhaps you could show me a working prototype of what you mean. As I still dont get ya!

Do it for you, you mean?

 

[Acidburn]

I guess so if you dont mind it would be really helpful and I would be really greatful!

 

[Mile-O]

This is basically what I mean although I'm aware monitors and computers could effectively be included with the Components Table - I've left these as separate tables.

I've not bothered with queries or form representations but these tables should give you an idea of what I mean.

 

[Acidburn]

Wow thats really really good! but i cant help but feel like theres not enought fields for where my information is needed to go. Wheres the sound card and etc? Comp make?

It could be me but when i clicked on compenet able it had 1, 2, 3, 4, 5 and next where the componets hmm My data base needs to store inforation about these... not return whats in it. if you follow me.

Hi again just been playing around i like what you've done! sorry about the above comments but it was very complex until i took the time to work out what was done. Hmm may i ask why have you got repeating fields in the tbl computers ? I mean the location and make ... or are they just links? Since i didnt have them before. Also why is this good? (better than before)?

 

[Mile-O]

i cant help but feel like theres not enought fields for where my information is needed to go. Wheres the sound card and etc? Comp make?

The sound card goes into tblComponents. The models of sound cards go into tblComponentTypes.

Comp make is in the tblComputerModels. It's a foreign key in tblComputers.

 

[Acidburn]

just entered some more information isto the tables then opend up a query to try and get some answers well I'm lost my end user is ment to be able to enter a location and out comes all the spec of all the pc's with that location field rather than this:

 

[Mile-O]

Okay, a very rough example - navigate through the records using the navigation buttons at the foot of the form : frmExample.


As for the location: you'd have a combobox (2 columns) - LocationID, Location with a ColumnWidth of 0;2.cm

After the update of the combo you'd requery.