Insufficent memory error

[hcts]

I am at a install with a new client. We have 9 new HP workstations, 1 gig ram, 80 gig SATA HD, symantec corporate ed anti vir, XP PRO SP2, Pdox runtime 9 SP2.

On one of the computers I have a client that started getting a error when running a report "insufficent disk space" that points to the user temp directory. Knowing that the user had plenty of disk space I cleared out the temp directory and then reinstalled runtime. Everything printed ok, until I exit the program and go back in. Second time in I cannot run that report again. I can go to another workstation and print the report fine. Checked the originating table for corruption, none found. I can reinstall the SP2 for runtime 9 and the report will work again, until the user exits and comes back in.

Any ideas?

James D. Howard

 

[hcts]

An update to my last post. I used system restore and restored the registry back to Thursday. No problem any more. Then I reinstalled a windows update for the agere systems modem. Bam, insufficient disk space error is back. Restore the registry again, everything is ok.

I have not a clue why a modem driver update would cause pdox to crash, but we are dealing with MS windows here.

James D. Howard

 

[kjjj]

It more than likely has to do with your BDE Admin.
Go to control panel ( for the BDE ADMIN. I switch to classic view upper left hand corner) click on the BDE drop down to SYSTEM > INIT click on help, goto index, type in system INIT settings and read I hope this helps I am a novice who experienced similiar problems.
Good luck, someone else might be able to guide farther

PS there are mem size limits check this site for those

http://mirwin.homestead.com/files/faqs/WinLimitations.html

 

[TonyMcGuire]

I think kjjj has it.

Possibly the modem install adds a BDE and modifies your registry to point to the 'new' (likely actually older) BDE install.

Did the modem install also include any 'extra' utilities?

Tony McGuire

http://www.thedbcommunity.com

"It's not about having enough time. It's about priorities.

 

[hcts]

Well, I didn't install the modem prior to it breaking, it was an automatic windows update. To the best of my knowledge the automatic update did not install any utilities. After I restored the registry and stopped the automatic update, the report has run fine.

I had the same error show up on the same day at two different clients. These are totally different locations and IT infrastructures. I have no idea what the trigger was of how I stopped it. At the second client I had her restore to her last update, 4/15/05. That fixed it.

While the first location was a relativly new install, the second has been running our application for over 3 years.

Strange one.

James D Howard