Correcting existing database

[thefourthwall]

Hello,

Because a manager liked my previous efforts at building a database, that manager dropped a new project on me: an existing database of cell phone users and their details.

There are 6100+ records in one table; there are fields for user information, cell phone model/brand/number, etc...

Still browsing through the forum looking for the best way to extract cell phone data from user data (for example) to create separate tables, and apologize if I missed existing posts on how to do this.

How to pull out data yet keep it "intact," i.e., make sure that (800) 555-1212 stays with (related to?) User1, etc...

Happy to provide any other information needed.

-thefourthwall

 

[thefourthwall]

I should add, after having read my earlier posting today, that I am neither very good nor experienced in Access,
and am overwhelmed with the task given me.

Is it ok to leave an existing table as-is, when the table is full of different types of data? If not, how to fix? Running a make-table query sort of works, but I'm
missing key information.

Please help,

thefourthwall

 

[GingerR]

Why don't you tell us the structure of your existing tables (i.e. table name, field names and data types, and some sample data). Why do you think you need to tweak it? what is your project's "goal"? What are you being asked to do? You say that the db is 'existing', so what is it that your mgr wants you to do exactly?

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244. Basics at

http://r937.com/relational.html

 

[PHV]

Anyway, have a look here:

http://r937.com/relational.html

http://www.devshed.com/c/a/MySQL/Understanding-SQL-Joins

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[thefourthwall]

GingerR,

You bet. Currently there is 1 table only. The database curerntly is used to track which cell phone numbers are
assigned to which employees, and what model/provider is
used. For example, John Doe might have an LG model VX8350
cell phone with Verizon as the carrier, with a phone
number of 518-555-1212.

The form currently used for data editing/entry is
difficult to use, not intuitive, and does not display
all relevant attributes of each user.

The 1 table contains fields for users, addresses,
cell phone model types, phone numbers (primary &
secondary), etc. From everything I have been
reading on tek-tips, this is a really bad design,
yet I am stymied in how best to improve the table.

The form is relatively easy, except I am having real
trouble with correctly implementing a combo box: if
you or anyone else can help there, I'll be glad
to provide more information.

Thanks,
thefourthwall

 

[thefourthwall]

A follow-up: I built a make-table query to create two separate tables, one for users and another for cell phones, but was unsuccessful ...

 

[PHV]

In order to create two tables you have to build two make table queries ...

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[thefourthwall]

Why two queries? <scratching head>

 

[PHV]

Syntax of a make table query:
SELECT ...
INTO SingleTableName
FROM ...
WHERE ...

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[GingerR]

So yes you need to fix your table structure. Maybe you need these sorts of tables:

TABLE: Employees
EmployeeID
EmployeeName


TABLE: PhoneManufactures
PhoneManufacturerID (Autonumber)
PhoneManufacturer (text: LG, etc)

TABLE: PhoneModels
PhoneModelID (Autonumber)
PhoneManufacturerID (Number, from above)
PhoneModel

TABLE: EmployeePhones (relates an employee to a phone)
EmployeeID (Number, from above table)
PhoneModelID (Number, from above table)
PhoneNumber

So depending on how you are working, you might want to have a form where you enter PHONE information: manufacturers and models. There might be a combo box whose recordsource is a list of PhoneManufacturers (from the PHoneManufacturer table) where you enter various model numbers for the diff manufacturers. Then you have an Employee-only form, where you enter employees. There could be a subform on that Employee form where you pick that Make/Model of phone they have and enter the phone number.

So, again, it depends on how you are working there--are there several people entering this info? are there reports and such based on the data? If i were you i'd build the tables as suggested above first and put some data in them and see if that helps you better envision what is going on.

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244. Basics at

http://r937.com/relational.html