Probably a stupid question...

[Fuga]

...but I decided some time ago never to take anything for granted with access and memory handling.

My db is growing too big to be funny. This is because of two tables. Now I´m thinking of "splitting off" one of them and then link it back.

As long as I don´t use data from the linked table, it won´t be in the memory, will it?

I have also been thinking about not linking the table, but use recordset stuff. Is this a better idea? Or is there perhaps a better way that I haven´t even thought about?

Fuga.

 

[Dave Eyley]

Hi Fuga,

How big is big?

Dave E

 

[Fuga]

Hi Dave E,

table 1 holds 370 000 records, increasing by a little more than 5 000 a day. This is the table I´m thinking of moving.

table 2 holds 250 000 records, increasing by 500 a day.

There are also smaller ones for various purposes.

When I checked just yet the db is 110 mb in size, but I know it´s a little less (maybe 90 mb) when properly repaired and comprised (is that the word?).

The lap top I primarily use this db on has 96 mb.

Fuga.

 

[Autoeng]

There is a very good paper on keeping database size and speed where it needs to be on http://www.fmsinc.com. Look under Resources - Technical Papers.

Autoeng

 

[Fuga]

Thanks everyone!

I´ve decided to go with Pat Hartman´s suggestion.

Also, it might be possible to delete 1-3 fields from the biggest table (at the expense of info of course).

Autoeng:

I would very much like to read the paper. However the link seems not to work. Maybe it´s my browser.

Fuga.

 

[Autoeng]

Updated the link and it should be good now. Take a look at all of the technical papers there as there are some good ones.

Autoeng

 

[Fuga]

Great! Thanks!

Now I know what to do for the rest of the day.

Fuga.