Thread: Normalization
View Single Post
  #16  
Old March 14th, 2010, 07:17 AM posted to microsoft.public.access.tablesdbdesign
John W. Vinson
external usenet poster
 
Posts: 18,261
Default Normalization

On Sun, 14 Mar 2010 06:21:40 GMT, "sys_analyst47 via AccessMonster.com"
u58607@uwe wrote:


So you want me to break the customer info, like Customer no, Name & Passport
number, and what about the vehicle information then ????


In a Vehicle table.

If i split it like
this how i will generate my contract which is based on mail merge & in mail
merge i think we can only take one table at one time..


You are mistaken.

You CAN base a mailmerge on a query.

As David Fenton pointed out in another thread, the query may not work if it
contains Access or VBA functions... but a simple join query *DOES INDEED* work
as the source of a mailmerge.

Even if it doesn't (for performance, or because you do need such a function),
you can maintain your data better if the tables are normalized. You can use a
(non-normalized) table as the source for the merge; empty it with a Delete
query and populate it with multitable data from your normalized queries with
an Append query.

Please suggest me if i
will generate a query based on the suppose non normalized customer table &
just fetch customer no,name, date based on that i make a table & then a form
for discrepancy and here i will just add one field for discrepancy. I know
its just a way out ...


I do not understand your question.

And if i split the customer info as mentioned above and vehicle info separate
?? the problem which i am looking is that how I will generate contract which
is purely replying on the above non normalized data ... or either i will make
a query which will take info from 2 - 3 tables and will create a table and
basis on that table i will generate the contract .. in addition to this a
user who is going to put information for the contract i will have to make a
sub form ???? means i dun want to make it complicated .. and I asked for the
wayout for searching like user put customer no in suppose combo box and the
information from other table will fetch in text box.


Don't confuse DATA STORAGE - in tables, normalized - with DATA DISPLAY - a
Report, a printed contract, which can be an Access Report, a MailMerge from a
query, perhaps a MailMerge from a temporary table, perhaps even generated
using VBA and Word automation. Unless your contracts are one-time-only
printouts and you never need to deal with repeat customers or other repeating
data, your maintenance will be much easier with normalized tables.

--

John W. Vinson [MVP]