I'm trying to get a handle on normalizing my database to better manage a
very large customer table. (1 million records...) My databases main
function is managing direct mail campaigns and the call results from the
mailing. The mail department gives me the names with the following
information:

IdString,ListCode,ListString,name,address1,address 2,city,state,zip,maildate
EXAMPLE: GA502-100358,GA502,100358,Norm Petersen,123 main street,apt
3,boston,MA,90210,02/28/2005

IdString = the code they customer uses when they call in, "account number",
primary key for customers table
ListCode = Foreign Key to the Lists table
ListString = a 6 digit number that is reset to 100001 each month, combined
with ListCode to create IdString and always keep it as a 6 digit number

I'd like to setup the customers table properly and effeciently so that I
have a solid foundation to build on when we start incorporating the ordering
process into this database. For reporting and maintenance I'm using Access
2002 "project" as a front end to SQL Server 2000 on a Windows Small Business
Server 2003 Premium server pc. For the actual sales reps handling the
incoming calls I'm using a web server program called "Resin" as a front end
to the same SQL Server back end.

I'm tracking call results for each list in the lists table, as well as stats
on each employee listed in a employees table. Most of the call result info
is stored in an orderinfo table that is essentially a 1-1 relationship with
the customers table. The "Resin" guru is working on normalizing that
portion of the project.

Any help would be appreciated.