Having repeating groups of fields is not normalized. All of your Vacation
fields belong in a related table
EmployeeNumber, VacationDate, VacationNote
Your Monday etc fields should also be broken out with a more normalized
structure.

Once you have your new tables created, you can use append queries to append
the records/values from your existing table.
--
Duane Hookom
MS Access MVP


"Westley" wrote in message
...
I played around with the Table Analyzer Wizard. Is there a way to not use
the wizard to split the database? I would like to have a few different
tables.

Employees (EmployeeNumber, FirstName, LastName, Address, City, State,
ZipCode, CellNumber, HomeNumber, BirthDate, HireDate, TerminationDate,
Salary, ReferredBy, VacationDay1, VacationNote1, VacationDay2,
VacationNote2, VacationDay3, VacationNote3, VacationDay4, VacationNote4,
VacationDay5, VacationNote5, VacationDay6, VacationNote6, vacationDay7,
VacationNote7, VacationDay8, VacationNote8, VacationDay9, VacationNote9,
VacationDay10, VacationNote10, MondayAM, MondayPM, TuesdayAM, TuesdayPM,
WednesdayAM, WednesdayPM, ThursdayAM, ThursdayPM, FridayAM, FridayPM, Notes,
DateCreated, UserCreated, Date Modified, User Modified, DateLeadsAcquired,
LeadsAcquiredAM, LeadsAcquiredPM, LeadNotes)

I would like the primary key to be EmployeeNumber on different tables. How
would I do this? how would I create lookup tables? what happens to my
original table?