Office 2003 - Acceess Not enough space on temporary disk

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jai_Friday - 20 Jul 2007 10:44 GMT

I have an ODBC report that has been created in Microsoft Access 2002
(10.6771.6825) Service Pack 3

This report Uses 5 Tables (Of which the size of data amounts to over 60
meg). The report works fine no problems at all.

When runnning the same Access database report on Microsoft Access 2003 it
errors with

[Microsoft] [ODBC Microsoft Accesss Driver] Not enough space on temporary disk

Is there any setting that can be applied via Access of Windows Registry to
allow the temp disk space to be expanded. It appears to be an issue with
Office 2003

Regards

Jai

Reply to this Message

Douglas J. Steele - 20 Jul 2007 11:33 GMT

How much free space do you have on your temporary disk? To find out where
your temporary disk is, open a DOS box and type set t. You should see at
least two environment variables defined: TEMP and TMP. Look where they
point.

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)

>I have an ODBC report that has been created in Microsoft Access 2002
> (10.6771.6825) Service Pack 3
[quoted text clipped - 15 lines]
>
> Jai

Reply to this Message

Jai_Friday - 20 Jul 2007 11:56 GMT

Both point to c:\docum~1\User\LOCALS~1\temp

where can you enlarge the space (I would of though it was related the size
of hard disk either way)

> How much free space do you have on your temporary disk? To find out where
> your temporary disk is, open a DOS box and type set t. You should see at
[quoted text clipped - 20 lines]
> >
> > Jai

Reply to this Message

Douglas J. Steele - 20 Jul 2007 12:52 GMT

It is related to the size of the hard drive. Many people partition their
hard drive partitioned, and forget to point the TEMP (and TMP) variables to
point to the largest drive.

How large is your back-end?

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)

> Both point to c:\docum~1\User\LOCALS~1\temp
>
[quoted text clipped - 29 lines]
>> >
>> > Jai

Reply to this Message

Jai_Friday - 20 Jul 2007 13:20 GMT

The Hard disk is a 200gig IDE unpartitioned.....

However the problem to arise with a mapped network drive the report was
running from when I got the inital problem, I then move the access database
local to the machine and still the same problem (That even when I did a
compress/repair on the database)

> It is related to the size of the hard drive. Many people partition their
> hard drive partitioned, and forget to point the TEMP (and TMP) variables to
[quoted text clipped - 35 lines]
> >> >
> >> > Jai

Reply to this Message

Douglas J. Steele - 20 Jul 2007 14:26 GMT

It doesn't matter where the MDB file resides: you're running it on your hard
drive. That's why we always recommend that you split your application into a
front-end (containing the queries, forms, reports, macros and modules),
linked to a back-end (containing the tables and relationships). Only the
back-end should be on the server: each user should have his/her own copy of
the front-end, ideally on his/her hard drive. (Having the front-end on your
hard drive will reduce network traffic.)

Assuming you've got plenty of space left on your hard drive (I'd say at
least 2 or 3 times the size of the back-end MDB file), and that your
back-end MDB file isn't close to the size limit (2 Gb), I'm afraid I have no
suggestions.

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)

> The Hard disk is a 200gig IDE unpartitioned.....
>
[quoted text clipped - 50 lines]
>> >> >
>> >> > Jai

Reply to this Message