Hi,

I am required to remove all old data in my old database (2007 version) for my new construction project. I can start inputing the data from primary key 1.

But, it is difficult to find out the function. I tried for few hours.... today

thz for your help in advance.

Hi

If you open each table and press Ctl + A to select all records in the table, you can just press the Delete key. If you have related tables with Referential Integrity set you'll need to delete the child records before the parent records, but you'll get a message telling you that you can't delete records because etc etc if that's the case.

Once all the records are deleted, Compact and Repair the db (Office Button, Manage) and all Autonumbers will start again from 1

Hi,

(IMG:style_emoticons/default/welcome2UA.gif)

You may also check out Bob's website for a utility called "Database Reset Tool."

Hope that helps...

If you are just looking to delete the data from tables here is a function that will do that. It will not effect the system tables generated by Access. You still have to do a manual compact and repair after running function before entering new data. This only works for non linked tables.
Bobs utility maybe more what your looking for.

Different folks have different meanings for the term "remove". Some folks think that means "tear 'em out and physically get rid of them". But another interpretation is "make them so I can't see them ... until I want to see them".

Are you (or someone else) ever likely to need or want to see those old records, for historical purposes/comparisons, or for ... giggles, or because I just remembered something and want to check ...?

If the answer is "yes", then consider that second interpretation above, and make those records disappear without removing them.

If the answer is anything else (e.g., "heck no! never!"), use the second interpretation and make those records disappear without removing them. I've run into too many situations where the owners/users are insistent that they would NEVER need the data ... until they need the data!

Best of luck!

The only absolute (never/always) I believe about databases is the inevitability of change. Things that will NEVER change, *always* do; and things that will ALWAYS be, *never* are.

Hi Jeff I agree with you you should not delete the data.

However some people just copy the database at years end and rename it with the year added to the name. The function I submitted would give them a clean database to start with after the manual compact and repair.

A better solution is to archive the data and have the ability to restore when needed if size is a problem, if not as you suggested just not make it visible.

Glen

That certainly works for some folks... until they want to compare "last year's" numbers with the current year. Then it gets sticky trying to connect (let alone find!) the older data.

Much easier, in the long run, to have all the data in one place, and only look at the "current" data... (the voice of painful experience!).

I hear you on that one but database size can become a problem if not split which reinforces the need to split every database ... (IMG:style_emoticons/default/thumbup.gif)

I've run across one user who'd db was facing a size crisis which (sorta) warranted using multiple dbs. He was collecting stock quotes, thousands of records per day, reasonably expecting to outgrow Access' size limit.

Other than that, until the OP describes the actual record size and growth expectations, I'll still stick with a single (back-end) db file.

Recently, I am busy with my new project and so i havent come back to this site.

anyway, thz a lot.

(IMG:style_emoticons/default/yw.gif)