ADO Not enough temporary disk space Error

[ChrisQuick]

Hello,

We have a web server application written in VB6 that uses ADO 2.5 to connect to a MS Access 2000 through a System DSN.

Occasionally we get an ADO error:
Not enough temporary space on disk
while opening a recordset.

The server itself has about a Gig of RAM,and several gigs free diskspace, so we don't know why we get this error.

Any ideas? cquick@geotg.com
Geographic Information System (GIS), ASP, some Oracle

 

[jmarler]

Check to see how much space has been allocated for the SwapFile. It doesn't matter how much free Diskspace you have if the Max size of the swapfile has been capped. - Jeff Marler

http://www.JeffMarler.com

(please note, that the page is under construction)

 

[ChrisQuick]

The swap file is set to about 480 Megs. cquick@geotg.com
Geographic Information System (GIS), ASP, some Oracle

 

[CuJo]

seems to me someone forgot to put a

on error resume next


in the program.....

can i ask why are you using ADO 2.5...????

you should be using Microsoft DAO 3.51.....

 

[ChrisQuick]

1) We have an On Error Resume Next directly preceding the line to open the recordset. It doesn't execute the error handle we have and STILL blows up on that line.

2) As to why we are using ADO, we have our reasons.
cquick@geotg.com
Geographic Information System (GIS), ASP, some Oracle

 

[Swany]

This is a common problem with large access databases. What is really happening is that the database either runs out of resources, file handles or heap.

The query you are executing probably returns an extremely large number of rows, or has a very complicated series of joins.

Try breaking the data down in steps to perform the same function using multiple queries, or reduce the number of rows returned by your recordset.

Also ensure you are not accessing linked tables via ADO sql statements. If you need to access tables in multiple data sources, take advantage of ADOs ability to merge multiple data sources into one recordset which will be more efficient.

If you continue to have problems with Access scalability you may want to consider a SQL server database, or Oracle database.