Since a couple of people here have already mentioned Unicode and
indexes (which "index" even when there isn't any data to index!), I'll
just mention that *how* you import that file can also be a cause of
bloat.
Since this is a tab delimited file, try just *linking* to the file and
using a query to import the file.
Also consider using a "temp" database that is just a container for the
file to be imported. This database should be separate from the
database you are using to do the import with. If memory serves, Tony
Toews has an example of creating and linking to a temp database on his
website:
http://www.granite.ab.ca/accsmstr.htm
On Thu, 25 Oct 2007 07:30:35 -0700, bobh <vu******@yahoo.comwrote:
>HI,
I understand AccessXP file size has a 2 gig limit but I trying to
understand the following
I have a tab delimited data file that is 1.3 gigs big and I try to
import it into an empty AccessXP database and it starts to import then
stops, I look at the database size and it shows 1.99 gigs.
AccessXP blots to almost twice the size of the import file??? is that
right?
Please Post Any Replies To This Message Back To the Newsgroup.
There are "Lurkers" around who can benefit by our exchange!