Access Error (Not Enough Space on the Tempory Disc)

[DonRayner]

Hi all, I've been fighting with this problem for a couple of days and hopfully someone here has an answer.

First off this is a comercial software package (JobBoss 5.02) using access 2000 runtime. the main mdb file is now at 1.33gb. The software is locked so I can't get at anything to make any changes.

Problem is occuring when accounting goes to close the month of septmber which will also close our year end (no choice) The program will run for about 30 seconds then come back with the error.

Access:-1812 [Microsoft][ODBC Microsoft Access Driver] Not Enough Space on Temporary Disk

Server Information:
Dell poweredge 1600sc
4gb memory
3gb free space on "C"
5gb free space on "D"
450gb free space on "K"

mdb is 1.33gb
compact repair was run on it in October

When I contacted customer support they suggested I try running it from another workstation that had more free space on "C". I did just that but it was no help.

I tried changing the MaxBufferSize and MaxRecordLocks settings for Jet in the registry but then all that hapened was it took longer to come back with the error.

Any Ideas?

[Stewart Ross]

Sorry Don, there's no obvious things you can investigate that you have not already done. Access has a limit of 2GB for any one table and 2GB for the total size of the DB, but the DB appears to be within limits at present. It is hard to predict what Access does internally as temp space is used in the normal operation of the DB engine - and only the vendor will be able to trace where within the database the errors are actually occurring.

I think this is clearly an issue for the vendor to resolve and not to fob you off with inadequate responses about available disk space.

-Stewart

[DonRayner]

Sorry Don, there's no obvious things you can investigate that you have not already done. Access has a limit of 2GB for any one table and 2GB for the total size of the DB, but the DB appears to be within limits at present. It is hard to predict what Access does internally as temp space is used in the normal operation of the DB engine - and only the vendor will be able to trace where within the database the errors are actually occurring.

I think this is clearly an issue for the vendor to resolve and not to fob you off with inadequate responses about available disk space.

-Stewart

I'll keep at the vendor, but I'm not going to hold my breath seeing what their inital responce was.....

Don