If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Testing DB and .....
I see two weakness in my db design. BTW I'm self taught so there are two I'm
aware of and many I'm not. I make a folder for my test db I can only run so many scenerios and move the relationship around so many times...when do you know when to stop? I start with a list of what I think I will ever need. Level 1 Reports and QUERY that we will need on a daily or weekly bases Level 2 Predict what we may need six months + down the road Create the tables.....I then find that I'm looking at as many as six to ten tables that seems like a lot. I can use a switchboard to keep the form count down...so should I be thinking in that direction or ? ? ? ? ? Archview Apartments 126 units over 250 people all with 2 vehicles....so it isn't that big of a deal My other project is creating something for the recording studio. Here I'm dealing with clients and billing not many though. A ton of information on songs, sounds used instruments used plug ins...when and what was edited back up information, submission information, ISRC Codes....that could be six or so tables. Suggestions Thanks Terry |
Thread Tools | |
Display Modes | |
|
|