I have a 16bit system. All of the sudden I am unable to bring up and save changes to a Stored Procedure unless it is much shorter than it used to be. I am no where near 64K. It isn't my computer settings as it does the same on another computer. The same thing happens with any larger Stored Procedures. They were fine a month ago, but now the only way I can make changes is to delete a bunch of lines at the same time (not always helpful). Any ideas?

Just as a clue, you can bring the file up, make changes, compile it (or save it) and it says it worked just fine. But then if you open the file back up, the changes are not there and they are also not in the compiled version. No error message occur, it just won't save changes unless you delete a bunch of lines.

It's been years since I've used the 16bit versions so I don't recall the limitations.

Are there inserts in the source code? This could push it over the 64K limit during compilation. Failure during compliation would disrupt the repository updates. ARev the source code limitation was 32K. You could save code ]32K and <64, just not compile it. Again, I don't recall the limitation in 16bit OI.

Probably the best thing to do other than upgrading to a 32bit version is to split the procedure into smaller programs.

The code is only 32xxx. There are no inserts. I was working but now many modules are too big. Something happend to make the size limit less. We have a 32bit product but many of our 16bit users can't afford to upgrade to it, meaning, I have to maintain both 16 and 32bit. Don't know why the size is all of the sudden a problem.

Debbie,

This has been a known problem. I was trying to search for previous posts on the issue to direct you but I haven't located any yet.

Have you installed any other software recently? I seem to recall that sometimes the size limit is related to the Window's common edit control. The version used can change depending on other software products being installed…although I don't think this would happen unless you were installing other 16-bit packages.

Are you getting any error messages in the statusbar of the System Editor? Are you still able to enter more characters in the program itself? IRC, when you reach the limit of the edit control you should get a message in the statusbar referring to the buffer limit.

One "technique" for working around this has been to pad the bottom of the programs with several rows of asterisks. I forget the reason why this helps, but sometimes it does. Then, if you start to get the buffer message you can remove asterisks as needed.

dbakke@srpcs.com

SRP Computer Solutions, Inc.

One discussion here

The Sprezzatura Group

World leaders in all things RevSoft

I pulled up the link but am still not sure what to do. The SP is 38843 characters. I can go in and delete a comment line. Press F9, or Compile and save. There are no messages and it says it saved ok. No clue anywhere. When I pull it back up, the line I deleted is still there. I tried adding * at the bottom to get it to 45000 characters. I saved it, no messages. When I bring it back up, the * that I added are gone. I have several SPs that are behaving this way. What do I need to do to get them to play nicely.

Programmatically add a few k of *. Then open the SP and delete some.

support@sprezzatura.com

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

I reformatted my laptop - because I was trying to fix this and changed my memory allocation. After that things went downhill. I reset my laptop to factory settings and reloaded everything. Now all is well. The problem went away. Thanks to all who responded.

View this thread on the forum...