How reliable or accurate is the MS Access 2000 "Table Analyzer" wizard

[kgreen]

How reliable or accurate is the MS Access 2000 “Table Analyzer” wizard at splitting tables with duplicate data ?

I have table in a inherited db that has hundreds of dup’ records but as the table as a whole has over 17000 records with 12 data fields per record, I am very loathe to start messing with it in case I mess up and loose data.

Can I trust the Wizard or is there a 3rd party developer add-in that will do the job. I know some of you will say that I can write code to do the job but that is simply beyond the level of my skill and will take me far too long. I am being pressed by my employers to get the job done – you guys must know how that feels, so any recommendations.

Kenny [sig][/sig]

 

[Robertd]

Hi Kenny,

Sorry i can't comment for 2000, but i've toyed with the access 97 (hey i design the schemma in the first place!)

but my advice is to set up a test database import your working database tables queries etc, etc then work on the test database to determin the results. keep in mind whilst removing duplicated data is the aim of a well designed relational database there are exciptions to the rule an obivious one is "point in time transactions" in some situations you might have to break the rules. other issues if you split the tables you will have to rewrite queries etc. for an established database this will be a big job to get the new model to reflect the origional design goals. using a test database will give you the chance to work out the pitfalls involved adapt the methods and reports without destroying the working database.

thats what i would do, no matter how good the conversion process is s-)

Robert [sig][/sig]

 

[kgreen]

Hi Robert,

Many thanks for taking the time to reply, I appreciate it.

Your comments contain some good advice that I will make sure to follow.

Thanks again,

Kenny [sig][/sig]