ExcelBanter

ExcelBanter (https://www.excelbanter.com/)
-   Excel Programming (https://www.excelbanter.com/excel-programming/)
-   -   64kB limit error (https://www.excelbanter.com/excel-programming/319277-64kb-limit-error.html)

Dave the Wave

64kB limit error
 
I am working on an Excel 97 application does that a great deal of VBA
processing. (The application should've been done in Access, but time and
budget constraints made Excel the tool of choice.) When I try to run one of
the procedures that I just added some more code to I get an error message
I've never seen before. "When compiled procedure exceeds 64kB memory
limitation....." is my approximation of the error response. I don't get
this message on my development machine, but I do on the machine where this
application is normally used.

I assume I have to break the procedure into smaller chunks to rectify this
issue; however, I would like to know a little more about the condition
before I just put a bandaid on it and send it back out.

I could not find anything on the MS website or via searches in some of the
news groups I know of. If someone has addressed thid issue before, please
send me a link to the resource/s.

Thanks in advance.

[email protected]

64kB limit error
 
I can't say from experience, but here's a thread that covers the
bases.

http://www.google.com/groups?hl=en&l...b61d7bf&rnum=7

HTH
Paul
--------------------------------------------------------------------------------------------------------------
Be advised to back up your WorkBook before attempting to make changes.
--------------------------------------------------------------------------------------------------------------

I am working on an Excel 97 application does that a great deal of VBA
processing. (The application should've been done in Access, but time and
budget constraints made Excel the tool of choice.) When I try to run one of
the procedures that I just added some more code to I get an error message
I've never seen before. "When compiled procedure exceeds 64kB memory
limitation....." is my approximation of the error response. I don't get
this message on my development machine, but I do on the machine where this
application is normally used.

I assume I have to break the procedure into smaller chunks to rectify this
issue; however, I would like to know a little more about the condition
before I just put a bandaid on it and send it back out.

I could not find anything on the MS website or via searches in some of the
news groups I know of. If someone has addressed thid issue before, please
send me a link to the resource/s.

Thanks in advance.




All times are GMT +1. The time now is 02:11 PM.

Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
ExcelBanter.com