How to prepare Normalized Data Model for Forms...

[RickDB]

Hello,

I have a fairly complete data model, my question is, how best to create tables for entry where I do not have subform after subform, and subforms in subforms. With subforms for the subforms and subforms on top of that.

I am about to start pulling out some teeth because at this point it sounds fun compared to this!

Do I need to use a query to base my table off of to build my Customer entry form? Or is my only option to use 15 frikin' Subforms? I I use a query, does that cause problems with data integrity?

I am having trouble finding useful reference to this, both online and in books I have purchased.

Normalization is fantastic, I understand.... But besides the crumby Northwind sample DB that everyone and their brother directs you to, is there an actual useful sample to look over that illustrates the use of a normalized data model?

I have grown more than a bit irritated with this, mainly because of my own inablilty to make progress in putting this project together.

I would like to create a simple to use, streamlined systems that promotes efficiency and speed, not a super convoluted system that has 85 subforms on every form in the DB.

I would REALLY appreciate some feedback/direction here, I am about to give up on normalized data and go with a simple flat table approach.

I would rather have redundant data than indecipherable forms that I have to answer incessant questions about.

Thank you,

- I am Rick's Utter Frustration

 

[RickDB]

From the sample I have provided in my previous post, I want to create a form for entry of customer information as the first step in my data entry process.

I understand I could base my form off of a query, but is that what I want to do? I am so lost on this it makes me sick. If I base this on a query, then afterwards, I will create a table, this table will have a entry box for Phone Number and Address. What if there are multiple of each? Isn't that the point of normalizing the table structure? How do I allow for entry of multiple numbers / addresses? The solution I see coming up is subforms, and what I have seen and created of subforms is very clunky.

I just had to elaborate a bit more for anyone who cares to read through this bore, but I am really hung up here and I just keep coming up with unrelated info/ or simply junk when I search for what I need.

Again, if anyone is aware of where a useful sample db can be found that work similiar to the model I have posted it would be so appreciated.

I am not wanting to copy either, I really want to learn how this works, and everything I have tried so far isn't getting me too far. I just need a strong sample of implementing any normaliaed data simliar to mine into useful forms, fast to use forms.

Thank you!!!

 

[The_Doc_Man]

From your description, it is possible that you are trying to do too much at once. I highly recommend Julius Caesar's methodology... divide and conquer.

You certain CAN use a direct form/table link if you wanted to. However, if you are running into normalization issues and too many queries, it is possible that your "too many queries" relate to LOOKUP queries. If I'm reading this wrong, sorry. However, you can use the form wizards to accomplish lookups without having to write a gazillion separate queries. Use combo boxes to look up something from a table and store a key-code instead of the thing being looked up. The form lookup wizard should be able to handle this for you.

If I have misread where you are going and the nature of your frustration, my original advice - divide and conquer - still stands. Try to not do too much at once on the form. This would be good advice even when you are NOT using Access to do your DB. Simplicity of the input form is the key to success. If you can't keep it simple, you might have a concept-level problem: Trying to do too much at once.