Search results

I'm a beginner and mentally wrestling with a many-to-many relationship. I have an IT equipment inventory database. The main table is All Equipment, and two lookup tables that it currently references are Manufacturer (where the choices for the Manufacturer field in the main table come from) and...

We had confused ourselves over the issues of recording items of equipment of different types, which had some common attributes but many attributes that only applied to one or two equipment types. Of course we now know that the common attributes mean those items of equipment must be recorded in...

Re: Question about equipment inventory database design Yes sloppy explanation on my part. All the EQUIPMENT will go into one table is indeed what I meant. That is an obvious step for you, but sadly hadn't been for me, because as I said I had been warping my use of tables. I had kind of...

Re: Question about equipment inventory database design No I was talking exlusively about my old misconceptions about the proper roles of tables and queries and relationships. I will DEFINITELY still be using lookup tables. But I will no longer be labouring under the misconception that by...

Earlier in this thread, I said: Entering printer data in the bottom row of a Printers Query achieves exactly this. So long as the Printers query includes all fields relevant to printers and no others. Of course it would still be nice to do it with forms, and have the form adapt to the...

Re: Question about equipment inventory database design In my first post I asked: My answer now would be: Simple. Collect all the data into one equipment table (as Bob said). It will have only one field for serial number. That will 'logically unify' the serial number field (and other fields...

Well, I've now amalgamated all of my fields from the various old tables,such as the old PC table; Monitors table; Printers table; Switches table etc. There is now just one big overall equipment table that covers all the types of equipment, and includes a new Type field that specifies what kind...

Yes we are (soon to be 'were' I hope). Actually the Inventory was originally (several years ago) in MS Excel. We did realise some of the benefits of using a proper database. But we were inexperienced in database design, and allowed considerations of data entry to affect table design. We do...

Dave (G-t-H), Thank you for your help. Actually this database already exists. It is fairly well developed.... in somewhat of the wrong direction. Merging the existing monitors, printers, computers, laptops, projectors, switches and other tables should actually not be massively difficult. Nor...

Thank you for this latest example. There is now a drop down list 'pool' of attributes, which varies depending on whether you pick laptop, monitor, printer or whatever. That is great. But this gives the user the option to pick and choose which laptop style attributes they are going to enter. I...

OK, I am reading them. I actually completely missed the hyperlinks first time, as I am pretty tired.

Point taken Maybe we were at cross purposes. I was actually trying to own up to a beginner mistake. Completely unfamiliar with forms, I was admitting that I HAD made the mistake of allowing my useage of tables to be dictated by data entry, because I was using them for data entry. I can see you...

I think you are saying that my division of the data into separate tables for different data types is a response to the problems of data entry. However it is the wrong response because I should be getting to grips with forms? I think you are saying that scrolling through reams of fields which...

Question about equipment inventory database design Hello, I am a relative beginner with MS Access. We are trying to create a database of all IT equipment in our large-medium size organisation. I have read about database design a bit and played around with the program, but I am facing a number...