Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
Bad DLL
Hi Big T,
Receiving this error message in a project that doesn't use any DLLs is a classic sign of minor code corruption. Download a copy of the code cleaner utility from my web site and run it on your project and it should cure the problem. -- Rob Bovey, MCSE, MCSD, Excel MVP Application Professionals http://www.appspro.com/ * Please post all replies to this newsgroup * * I delete all unsolicited e-mail responses * "big t" wrote in message ... Hi everyone, I'm using Windows 2000 and Excel 2000 (9.0.6926 SP-3). When i run a simple piece of code I get this error message: Run time error '49': Bad DLL calling convention but I'mnot calling any DLL!!!!! What's going on??!?!?!??!? Any ideas??? TIA big t |
#2
Posted to microsoft.public.excel.programming
|
|||
|
|||
Bad DLL
thanks Rob, I'll try that out. I've had this probelm intermittently with other Excel apps and it's really frustrating. Can you tell me any more about how your code cleaner works?
thanks big t "Rob Bovey" wrote: Hi Big T, Receiving this error message in a project that doesn't use any DLLs is a classic sign of minor code corruption. Download a copy of the code cleaner utility from my web site and run it on your project and it should cure the problem. -- Rob Bovey, MCSE, MCSD, Excel MVP Application Professionals http://www.appspro.com/ * Please post all replies to this newsgroup * * I delete all unsolicited e-mail responses * "big t" wrote in message ... Hi everyone, I'm using Windows 2000 and Excel 2000 (9.0.6926 SP-3). When i run a simple piece of code I get this error message: Run time error '49': Bad DLL calling convention but I'mnot calling any DLL!!!!! What's going on??!?!?!??!? Any ideas??? TIA big t |
#3
Posted to microsoft.public.excel.programming
|
|||
|
|||
Bad DLL
Hi Big T,
The code cleaner exports all of the standard modules, class modules and UserForms contained in your project to text files. It then deletes them all from your project and imports them back into the project from the text files. Since none of the excess junk that tends to build up in VBA projects is saved in the exported text files, this has the effect of removing that junk from your project. -- Rob Bovey, MCSE, MCSD, Excel MVP Application Professionals http://www.appspro.com/ * Please post all replies to this newsgroup * * I delete all unsolicited e-mail responses * "big t" wrote in message ... thanks Rob, I'll try that out. I've had this probelm intermittently with other Excel apps and it's really frustrating. Can you tell me any more about how your code cleaner works? thanks big t "Rob Bovey" wrote: Hi Big T, Receiving this error message in a project that doesn't use any DLLs is a classic sign of minor code corruption. Download a copy of the code cleaner utility from my web site and run it on your project and it should cure the problem. -- Rob Bovey, MCSE, MCSD, Excel MVP Application Professionals http://www.appspro.com/ * Please post all replies to this newsgroup * * I delete all unsolicited e-mail responses * "big t" wrote in message ... Hi everyone, I'm using Windows 2000 and Excel 2000 (9.0.6926 SP-3). When i run a simple piece of code I get this error message: Run time error '49': Bad DLL calling convention but I'mnot calling any DLL!!!!! What's going on??!?!?!??!? Any ideas??? TIA big t |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|