03-29-2006, 02:25 PM
This particular database contains three tables.
The first is a combination of data imported from five CSV files, each representing a quarter-year. So, we're due for a new one, shortly.
The others are the results of two different make-table queries. These tables are used by Excel in two different PivotTables, which is much faster than drawing the information from the first, gigantic, table.
The 2GB limit is reached.
The workaround I've come up with (but don't like) is making those five CSV files into linked tables.
Now, the database is really small, but also really slow. I've forfeited the indexing that was made possible by my original table, so the daily 20-minute data crunching session is now a 2-hour daily data-crunching session.
I guess it's not really a workaround I'm seeking, as I've already got that; set it up to run overnight.
But is my only option for avoiding the 2GB wall to structure the database in such a way that I can no longer use many time-saving features?
Oh, and I can't use FileMaker. :-(
GtDS
The first is a combination of data imported from five CSV files, each representing a quarter-year. So, we're due for a new one, shortly.
The others are the results of two different make-table queries. These tables are used by Excel in two different PivotTables, which is much faster than drawing the information from the first, gigantic, table.
The 2GB limit is reached.
The workaround I've come up with (but don't like) is making those five CSV files into linked tables.
Now, the database is really small, but also really slow. I've forfeited the indexing that was made possible by my original table, so the daily 20-minute data crunching session is now a 2-hour daily data-crunching session.
I guess it's not really a workaround I'm seeking, as I've already got that; set it up to run overnight.
But is my only option for avoiding the 2GB wall to structure the database in such a way that I can no longer use many time-saving features?
Oh, and I can't use FileMaker. :-(
GtDS