Recent content by littleme

Hello again... Im fiddled around with my database structure and landed back where I started.(thank you magicman) Work for a architects office and am trying to set up database to help describe all the rooms in a project, in terms of materials, equipment etc. there are 4 re-occuring sturcture...

Thank you all of you, but especially MagicMan. I think I finally get it! The penny has dropped.... I really appreciate all the help and admire the fact that you all took time and energy to help a complete stranger. A small step towards world peace.

Thank you for the input. A bit mind boggling at first sight but I hope I'll get it once I sit down with it. >>I think a little more description of your real world situation would help enormously. Ok: Each room has a unique room number. After having created a rough plan of a building, we sit...

I see where youre going, but what you're desribing is not really how we work. I agree with you that there will be certain Styles (be it doors, windows or entire rooms) that can be defined "outside" of the main table. Thats my next step. We work alot with predefined national styles already; thats...

I have no table 1. Was planning on have a new database file for each project. so only have table 2. And maybe not hundredS of fields per room, but certainly 100.

Ok... here's what I have so far. Its really only the beginning of it. Havent wanted to set the whole shebang up without understanding the principle of it. Also posting a PDF of the desired end result (according to my boss) where all the titles under the headings are some of the necessary fields...

Now I'm getting confused. (sorry) If splitting the tables up with 1:1 is not recommended and neither is having all information related to a room record in one table then what are my options...?

>>"So you end up with lost of records, not lots of fields." Got it. >> "Question, are the hundreds of fields associated with one room, or one project?" One database per project. Tons of rooms per project. Tons of fields per room. (Gonna try to eliminate less important fields)

what a luxury to have people answer this quickly. If my co-workers could be as prompt... None of the fields concern blueprints/diagrams. What i need the database for is to keep track of is color schemes, electrical needs, number of sockets, airflow, door widths etc for each room... Up till now...

>>"Hundreds of fields is a very bad thing."... What should I do then? >>"An example would be an order (or invoice/quote/purchase order). The order has "header" information (the parent) with the order number, customer, shipping information, special info, etc. and "detail" information (the...

hmm...so hundreds of fields are "ok"? Makes things easier in every way. What if I were to keep the tables that the other consultants are meant to fill out separate (since they dont always do as theyre meant to and leave things blank) What happens when records are deleted in "my" table? Are they...

Having searched the net and read a bunch of posts, Ive realised that Ive set up my database wrong. Ive read up on normalizing and so forth but am still a bit usure... I work for an architects office. Would like to use Access to organize the informations attatched to each room number in a...

Ah...ok. Thank you... So in my case: Dim I as integer For I=Min to Max Next I I see how that would run through the values...how do i put them in the combobox? :confused:

Hello again. Am hoping once again that someone can point me in the right direction. Have cascading comboboxes, which work fine. Only small hick-up... Have a table with fldSize fldMin fldMax CboxSize allowes user to choose a Size. What I then would like is for cboxLimit to populate with the all...

Sorry havent gotten back to you earlier. Thank you!