Not enough space on temporary disk - Error message

Hi All

Please can someone tell me how to resolve this.

Server running SQL Server 2000
Client running Windows XP
MS Access 2005

I have linked to a SQL database using ODBC drivers and have a number of
update queries listed in a Macro.

The first few queries run without a problem, but as soon as I get to one
of the tables which have a large number of records I get the error and
execution of the Macro halts.

I have replaced the macro with a VBA function which expresses the
queries as docmd.runSQL and I get the same result.

There is ample space on both the server and the client.

Thanks.

Laetitia

*** Sent via Developersdex http://www.developersdex.com ***

Re: Not enough space on temporary disk - Error message

On Oct 23, 2:26 am, Laetitia Clark wrote:
> Hi All
>
> Please can someone tell me how to resolve this.
>
> Server running SQL Server 2000
> Client running Windows XP
> MS Access 2005
>
> I have linked to a SQL database using ODBC drivers and have a number of
> update queries listed in a Macro.
>
> The first few queries run without a problem, but as soon as I get to one
> of the tables which have a large number of records I get the error and
> execution of the Macro halts.
>
> I have replaced the macro with a VBA function which expresses the
> queries as docmd.runSQL and I get the same result.
>
> There is ample space on both the server and the client.
>
> Thanks.
>
> Laetitia

I would

research "maxlocksperfile" which seems to be a common cause of the
problem you describe; there are several posts about it in cdma and ms
has at least one kb article about it;

or

assuming these are action queries, (they insert, update or delete),
run them through an ado connection; I'm guessing the Access registry
setting for maxlocksperfile will not affect that; I have no experience
showing that changing to ado will help but, with ado, I've never had
the problem you describe.

Re: Not enough space on temporary disk - Error message

On 23 Oct 2007 06:26:40 GMT, Laetitia Clark
wrote:

Open Control Panel > System > Advanced > Environment Variables and
check what the TEMP environment variable points to. Make sure that
drive has enough (>1 GB) disk space.

-Tom.


>Hi All
>
>Please can someone tell me how to resolve this.
>
>Server running SQL Server 2000
>Client running Windows XP
>MS Access 2005
>
>I have linked to a SQL database using ODBC drivers and have a number of
>update queries listed in a Macro.
>
>The first few queries run without a problem, but as soon as I get to one
>of the tables which have a large number of records I get the error and
>execution of the Macro halts.
>
>I have replaced the macro with a VBA function which expresses the
>queries as docmd.runSQL and I get the same result.
>
>There is ample space on both the server and the client.
>
>Thanks.
>
>Laetitia
>
>*** Sent via Developersdex http://www.developersdex.com ***

Re: Not enough space on temporary disk - Error message

Thanks, Lyle.
I have run into the MaxLocksPerFile error before and have had to change
the registry values in the past, but this is another error altogether.

I restored the customers database onto my laptop and the whole update
process ran through without a problem.

The problem only occurs on site so it seems to be one or more settings
either on their server or on the client PC.

Laetitia

*** Sent via Developersdex http://www.developersdex.com ***

Re: Not enough space on temporary disk - Error message

Hi Tom.
Thanks. That sounds like a promising solution. I will get the customer
to check it in the morning.
I will let you all know the result.
Thanks again.
Laetitia



*** Sent via Developersdex http://www.developersdex.com ***

Re: Not enough space on temporary disk - Error message

Hi Tom
THANKS !!!!
The customer checked the TEMP environment variable and found that it was
pointing to the C drive where they had 10 GB free space. Now that may
sound like enough, but the SQL database is huge and the log file grows
very fast when we do these updates.
I asked him to point to the E drive where they have 180 GB and the whole
process ran through without a hitch.
We have shrunk the log file back down and everything is working
beautifully.

Thanks again for your kind assistance.
Laetitia.



*** Sent via Developersdex http://www.developersdex.com ***