large database

[Guest]

I have a large database (13 m records). I need to haev a search form for our
customer service who take phone call and query the data.

But anything I try to do with the table ... results in either freezing or
extensive long time.

any ideas on how to work around?

also out of the 7 fields.. 3 are repeated (name, postcode, & ID) . so might
be a good idea to delete duplicates in that field.. but I dont know how to do
that?

any help appreciated...

 

[Joseph Meehan]

I have a large database (13 m records). I need to haev a search form
for our customer service who take phone call and query the data.

But anything I try to do with the table ... results in either
freezing or extensive long time.

any ideas on how to work around?

also out of the 7 fields.. 3 are repeated (name, postcode, & ID) . so
might be a good idea to delete duplicates in that field.. but I dont
know how to do that?

any help appreciated...

It sounds like you may have a table that needs to be normalized. That
would be a good start.

 

[John Vinson]

I have a large database (13 m records). I need to haev a search form for our
customer service who take phone call and query the data.

But anything I try to do with the table ... results in either freezing or
extensive long time.

any ideas on how to work around?

also out of the 7 fields.. 3 are repeated (name, postcode, & ID) . so might
be a good idea to delete duplicates in that field.. but I dont know how to do
that?

any help appreciated...

As Joseph says, normalizing this database would be an excellent first
step. If you have multiple calls per person, probably two tables would
be good. Indexing all fields used in sorting and searching will be
essential.

People
PersonID <Primary Key, autonumber or other unique ID>
LastName <indexed, nonunique>
FirstName <indexed, nonunique, if you search by it>
PostCode <indexed, nonunique>

Calls
CallID <primary key, autonumber>
PersonID <in a one-many relationship to People>
<information about the call>

13 million records is pretty hefty, but with proper indexing and query
design should be well within the capabilities of Access.

John W. Vinson[MVP]