By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,503 Members | 2,788 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,503 IT Pros & Developers. It's quick & easy.

Access 97 Database Size and Linked Tables

P: 2
I know that the max size limitation for a 97 Acesss Db is 1 GB. I have been trying to determine how much, if any, the size of the database is reduced by linking a large Access 97 table from another Access 97 Db compared with storing that same table within the database itself. The testing I have done so far appears to show no difference. Are there are stats available on this anywhere? Thank you in advance for any information on this subject.
Dec 29 '06 #1
Share this Question
Share on Google+
3 Replies


nico5038
Expert 2.5K+
P: 3,072
Tablespace isn't used in the database when you link a table. (Only a small amount to store the link information)
You'll have to compact & repair the database however after moving a table to another database, else the used tablespace won't be freed up by Access !

Nic;o)
Dec 29 '06 #2

P: 2
Tablespace isn't used in the database when you link a table. (Only a small amount to store the link information)
You'll have to compact & repair the database however after moving a table to another database, else the used tablespace won't be freed up by Access !

Nic;o)
Thank you for the prompt reply. That would have been my expectation. What I did was insert data records via VBA code (large amounts) into linked tables in a fully compacted database 'primary.' As I said in my original post, these tables are resident in another Access 97 Db. What happens is that there is no difference in the resulting size of the 'primary' database after the insert as compared to inserting the same data into the tables as if they are resident in the 'primary' database.' As a further test, I removed the linked tables entirely from the 'primary' Db, compacted again, while leaving the tables still in a separate Db. I performed the same insert to these tables directly from one Db to another. In this instance, the 'primary' database had marginal size growth and the Db holding the data tables grew to about 1/2 the size of the 'primary' Db under the earlier tests. Since I am starting to exceed the 1 GB Db limit, I am needing an alternate solution. It looks like holding the tables in a separate Db and inserting directly is the way to go.

Thanks again for your response.
Marmadmax
Dec 29 '06 #3

nico5038
Expert 2.5K+
P: 3,072
Upgrading to Access 2000 will give a 2Gb space, but you can also use the free MySQL or the free (limited) MS SQL download from Microsoft.
Even Oracle (10g) is free available.

Nic;o)
Dec 29 '06 #4

Post your reply

Sign in to post your reply or Sign up for a free account.