Access 2003: Not enough space on temporary disk. (Error 3183) Win10

[holeg]

Access App works fine using Win XP
But not in Win10
App+Tables mdb rebuildt/compressed ok, linking ok but

Access 2003: Not enough space on temporary disk. (Error 3183) under Win10 64bit

Quick fix ?????

[Homegrownandy]

https://msdn.microsoft.com/en-us/lib...ffice.12).aspx

[holeg]

Thanx,I've checked this on and found
TMP + TEMP = c:\Windows\Temp
cdrive has 90GB free
However calinng to open form1 is having a subform form2 and only selecting one record...
Hmmm

[Homegrownandy]

Is that due to the first issue? are you still getting the error?

[holeg]

Same error 3183, changed my users TMP and TEMP to c:\temp
Reboot pc but same error. Disk space is the limit her or not ?
I Do not see where to limit/upgrade temp storage..

[holeg]

Sorry, I ment: I Do not see where to limit/upgrade temp storage size
I'm thiking it depends on the free disk space available but not 100% sure..

[holeg]

Query sql code:
SELECT Ordrer.Ordrenummer AS Uttr1, Ordrer.Tilbudsnummer AS Uttr2, Ordrer.KundeNummer AS Uttr3, Kunder.KundeNavn AS Uttr4, Ordrer.BestillingsDato AS Uttr5, Ordrer.Serienummer AS Uttr6, Ordrer.ProduksjonStartDato AS Uttr7, Ordrer.Leveringsdato AS Uttr8, Ordrer.Merverdiavgift AS Uttr9, Ordrer.FritekstfeltOrdrebekreftelse AS Uttr10, Ordrer.FritekstfeltFaktura AS Uttr11, Ordrer.NavnForLevering AS Uttr12, Ordrer.AdresseForLevering AS Uttr13, Ordrer.PostnummerOgStedForLevering AS Uttr14, Ordrer.TelefonnummerForLevering AS Uttr15, Ordrer.KontaktpersonForLevering AS Uttr16, Ordrer.Kontaktperson AS Uttr17, Fakturering.Fakturanummer AS Uttr18, Fakturering.Fakturadato AS Uttr19, Fakturering.FerdigFakturert AS Uttr20, Fakturering.BetaltFaktura AS Uttr21, Fakturering.InnbetaltDato AS Uttr22, Ordrer.SlettOrdre AS Uttr23, Ordrer.OverstyrUtkjøringsdato AS Uttr24, Ordrer.OverstyrUtkjøringsUkedag AS Uttr25, Ordrer.Internordre AS Uttr26, Ordrer.Internmelding AS Uttr27, Ordrer.Betalingsmerknader AS Uttr28
FROM Kunder, Ordrer, Fakturering
WHERE (((Ordrer.Serienummer) Is Not Null) AND ((Ordrer.SlettOrdre)=False))
ORDER BY Ordrer.Ordrenummer;

[holeg]

Same error for this query SQL as well.
SELECT Ordrer.Ordrenummer AS Uttr1, Ordrer.KundeNummer AS Uttr2, Kunder.KundeNavn AS Uttr3, Ordrer.BestillingsDato AS Uttr4, Ordrer.Serienummer AS Uttr5, Ordrer.Leveringsdato AS Uttr6, Ordrer.Merverdiavgift AS Uttr7, Ordrer.FritekstfeltOrdrebekreftelse AS Uttr8, Ordrer.FritekstfeltFaktura AS Uttr9, Ordrer.NavnForLevering AS Uttr10, Ordrer.AdresseForLevering AS Uttr11, Ordrer.PostnummerOgStedForLevering AS Uttr12, Ordrer.TelefonnummerForLevering AS Uttr13, Ordrer.KontaktpersonForLevering AS Uttr14, Ordrer.Kontaktperson AS Uttr15, Fakturering.Fakturanummer AS Uttr16, Fakturering.Fakturadato AS Uttr17, Fakturering.FerdigFakturert AS Uttr18, Ordrer.SlettOrdre AS Uttr19, Ordrer.OverstyrUtkjøringsdato AS Uttr20, Ordrer.OverstyrUtkjøringsUkedag AS Uttr21
FROM Kunder, Ordrer, Fakturering
WHERE (((Ordrer.Serienummer) Is Null Or (Ordrer.Serienummer)=0) AND ((Ordrer.SlettOrdre)=False))
ORDER BY Ordrer.Ordrenummer;

[holeg]

2 MDB files only: program.mbd 36mb, tables2003.mdb 23mb
Time to upgrade to acces 2013 or 2016 ? May introduce more challenges/issues ?
Tried access2016 but date issues and ocx's missing then...

[holeg]

number of records in the respective tables in tables2003.mdb reduced
to just av few ( ie orders table only 3 records etc....)
However, I'm still getting the error 3183
=> Not enough space on temporary disk. (Error 3183) under Win10 64bit and Access 2003.
All tips and trix 4 a solution are welcome !

[Homegrownandy]

Is the issue specific to this database? Try to replicate the error in a new DB. It might help narrow down what's causing it. Perhaps the query is set up in such a way that its returning too many values. Do basic query's work? try just showing a list of information. Even if your order table has three records. do you also have other tables open in that query window.

[holeg]

Hi, solution found using another backup (copy found on server/ local disks etc... a bit messy but... not my pc)
and then after hours of testing, linking, compressing, ocx reg etc... A solution was found.
Made a 'how2 install proc' now for my friend. vs future installs...

Ref your reply: The Issue was specific to this database. Even started deleting records but that was not the solution in this case.
[ended up deleting too much and relations failed giving other new errors :-( ]

As stated above: Finally came across another 'hidden' copy of the application mdb on my collegaues pc:
re-linked to the tables mdb + compress and it worked fine
on my test pc with winXP sp3. Solution then tested under win10 as well and seems to work as normal as well.
Will test on another new pc at my colleagues tomorrow when remote access will be set avail again :-)

Thanks for your advices, much appreciated. Not easy to know when MDB's are not 'at your hands'.
But all advices and forum searches paid off... pointing me in the right direction...

Do you do upgrades from 2003 to 2013/2016 for a set price quote? Just asking in case you do :-)
By the way, not my access code, Embarc. Delphi Programming is my favorite :-)

Thanks again !!!

[Homegrownandy]

 Do you do upgrades from 2003 to 2013/2016 for a set price quote

I'm not sure what you mean by that, but I am glad you have this working. I don't feel like I was much help at all haha.
Du er bra! (my attempt at encouragement in Norwegian)