error message "not enough space on temporary disk"

  • Thread starter Thread starter Randal
  • Start date Start date
R

Randal

This happens when I run an update query on a table containing 4230786
records. I have at least 40 GB free space. Is there a setting I can change
in Access to allow it to use more disk space?
 
Hi,

It is limited to 2Gig ( plus another two gig in a temp file if temporary
storage is required for a query resolution, as example).



Hoping it may help,
Vanderghast, Access MVP
 
Michael
Sorry to impose but I ran across the same problem and can't find anything in the MS KB
I'm running an update query in Access 2003 under Win XP Pro. The total database is about 1 gig and I have 4 - 6 Gigs free on each of my three partitions so I wouldn't think space would be a problem. The update query simply updates only one field that represents 36,652 records
I'm really frustrated and have no clue what to do
Any help will be appreciated
Thanks.
 
1) Message typically means, not enough space on temporary disk.
Where is your temp folder?

2) How are you running query? will it run from db.Execute or
from macro with Transactions turned off?

(david)

P Straube said:
Michael,
Sorry to impose but I ran across the same problem and can't find anything in the MS KB.
I'm running an update query in Access 2003 under Win XP Pro. The total
database is about 1 gig and I have 4 - 6 Gigs free on each of my three
partitions so I wouldn't think space would be a problem. The update query
simply updates only one field that represents 36,652 records.
 
When you run query from within macro, there is an option for turning off
transactions.
Look immediately below the query name for the second entry field.
Transactions use
the temp folder for the transaction file. Sometimes badly formed queries
just use up
2GB of transaction space, which is the maximum before getting this error
message.

(david)

P Straube said:
David,
Thanks for your response.
My Temp folder is C:\temp. That drive has 10.6 Gig free.
Unfortunately, I have no idea what "db.Execute" is. I have run the query
within a macro and simply on its own with the same result.
 
Back
Top