Visual Basic/VB, At wits end-out of memory

At wits end-out of memory

Author	Message
Bill MacIntyr #1 / 2	At wits end-out of memory Please help. My app is giving an out of memory error (error 7) just after it starts to load. It is a 1.2 MB exe connecting to 2 Access databases using DAO. I have tried it on 7 machines at work as low as a P75 with 16 MD ram and it runs fine. The resource meter does not go below 83% throughout the app. The problem is with a sale of the app to a client who cant get it to run on the clients machine and another he has at his shop. The person who installed it originally had it running on a 486 DX266 with 16 MB ram but after I gave him a new version with very few changes- nothing major, it gives the out of memory error. He ipgraded the clients machine to a P75 with 32 MB ram and it still wont run. He also tried to run it on a P233 at his shop and had the same problem. The only thing I can see that is common on the machines he is having the problem with is a common brand motherboard (cheap) and only 256K cache (I think on both machines). I thought I had it nailed down to a problem with registering FM20.DLL. On my machine at home, I renamed FM20.DLL and tried running the app. I got the same error 7. After I renamed FM20 back and registered it with REGSVR32.EXE, the app would run again. I had the guy that is having the problem try the same thing (REGSVR32 FM20.DLL) but it didn't help. Is there anything that can commonly cause such an error. Is it a VB problem? What are VB's requirements for cache, Ram processor etc? We also had a client that installed one of our other apps call our tech support with the same problem. That particular app was a much bigger app with a ton of graphics in the exe. Bill MacIntyre Moncton NB Canada
Thu, 12 Apr 2001 02:00:00 GMT

Dou #2 / 2	At wits end-out of memory Bill: This is a spurious message. It is probably caused by a control that is not registered properly. That is usually when I have received the message. Check any OCX files that you are distributing to be sure they are registered properly. Also, some OCX files have dependent DLLs. Be sure that they are also registered properly. I have also received this error when trying to run components on a remote machine, through DCOM. The problem was that the component was not set up correctly in DCOMCNFG. However, if DCOM is not involved, your problem is probably a registration problem on one of the files that you are distributing or one of the dependent files. Some OCXs ship with dependency information. It wouldn't hurt to check that. In any case, your problem is almost certainly NOT related to a lack of memory. Doug says... Quote: > Please help. > My app is giving an out of memory error (error 7) just after it starts to > load. > It is a 1.2 MB exe connecting to 2 Access databases using DAO. > I have tried it on 7 machines at work as low as a P75 with 16 MD ram and it > runs fine. The resource meter does not go below 83% throughout the app. > The problem is with a sale of the app to a client who cant get it to run on > the clients machine and another he has at his shop. > The person who installed it originally had it running on a 486 DX266 with 16 > MB ram but after I gave him a new version with very few changes- nothing > major, it gives the out of memory error. He ipgraded the clients machine to > a P75 with 32 MB ram and it still wont run. > He also tried to run it on a P233 at his shop and had the same problem. The > only thing I can see that is common on the machines he is having the problem > with is a common brand motherboard (cheap) and only 256K cache (I think on > both machines). > I thought I had it nailed down to a problem with registering FM20.DLL. > On my machine at home, I renamed FM20.DLL and tried running the app. I got > the same error 7. > After I renamed FM20 back and registered it with REGSVR32.EXE, the app would > run again. > I had the guy that is having the problem try the same thing (REGSVR32 > FM20.DLL) but it didn't help. > Is there anything that can commonly cause such an error. Is it a VB problem? > What are VB's requirements for cache, Ram processor etc? > We also had a client that installed one of our other apps call our tech > support with the same problem. That particular app was a much bigger app > with a ton of graphics in the exe. > Bill MacIntyre > Moncton NB Canada
Fri, 20 Apr 2001 03:00:00 GMT

Page 1 of 1

[ 2 post ]