Bulk Copy (Suggestions Please ?)
-
Working with Access 2000 Database and ADO(Visual C++) My Database tables and their relationships resemble a Tree or a Family tree. (ie a lot of one-to-many relations between father/child tables) The task is to keep the size of the database within certain limits. As the database grows beyond certain limit, i would like to keep the latest N records and delete the old stuff. Unfortunately, this doesnt seem to reduce the size of the database (I don;t know why) may be because I am using "Autonumber" fields. The second step would be to reindex my autonumber fields so that I don't run over the limit of long integer datatype. Please help with some tips on how to approach. Thanks
-
Working with Access 2000 Database and ADO(Visual C++) My Database tables and their relationships resemble a Tree or a Family tree. (ie a lot of one-to-many relations between father/child tables) The task is to keep the size of the database within certain limits. As the database grows beyond certain limit, i would like to keep the latest N records and delete the old stuff. Unfortunately, this doesnt seem to reduce the size of the database (I don;t know why) may be because I am using "Autonumber" fields. The second step would be to reindex my autonumber fields so that I don't run over the limit of long integer datatype. Please help with some tips on how to approach. Thanks
You have to use "Compact and Repair Database" from the Tools->Database Utilities menu to shrink a database after records are deleted. This can also be done programmatically.
-
You have to use "Compact and Repair Database" from the Tools->Database Utilities menu to shrink a database after records are deleted. This can also be done programmatically.
-
How to do it programatically ? Any solution to "Autonumber" field running out of limits ? Thanks
How to do it programatically ? Microsoft Knowledge Base Article - Q230501 Any solution to "Autonumber" field running out of limits ? Autonumber is a long integer, which will give slightly more than 2 billion numbers. If you will have more than 2 billion records, you can either use a compound key or create an unpopulated table when you reach 2 billion and start fresh.
-
How to do it programatically ? Microsoft Knowledge Base Article - Q230501 Any solution to "Autonumber" field running out of limits ? Autonumber is a long integer, which will give slightly more than 2 billion numbers. If you will have more than 2 billion records, you can either use a compound key or create an unpopulated table when you reach 2 billion and start fresh.
I would suggest that access doesn't scale well to two billion records. Signature space for rent. Apply by email to....
-
I would suggest that access doesn't scale well to two billion records. Signature space for rent. Apply by email to....
Jon Hulatt wrote: I would suggest that access doesn't scale well to two billion records Or even a couple of thousand in most cases :) Paul
-
I would suggest that access doesn't scale well to two billion records. Signature space for rent. Apply by email to....
Granted, Access doesn't scale well to 2 billion, but he intends to archive excess records and only keep N (hopefully a fairly small number) records online. I've had success with Access up to about 200K records. More than that typically causes it to blow up.