Windows 2000. OI 3.61 single user developer. Suddenly in one of my stored procedures a search with System Editor is unable to find anything. Any search fails. It's not like some have reported where the search is successful but the window doesn't scroll - the status line says "Passed end of record!". Closing and restarting OI doesn't work. Anybody seen this before?

The stored procedure is 40,195 characters long.

- Oystein -

Hi Oystein

I've got procedures with more chars than that (over 50K I think) and the search still works.

Did you try shutdown, count to ten, start up, as well as the close OI and open again. I find weird things happen when the system thinks it has run out of memory, and only a shutdown will fix it.

And people wonder why I only have my mail system open when I want to check my mail, instead of having it open all the time and notify me when mail shows. Doesn't seem to matter how much RAM I get, it always seems better to close any apps not in current use.

Scott, LMS

4 reboots a day.

Scott,

I've got procedures with more chars than that (over 50K I think) and the search still works.

First, we are using Windows 2000 as well. Sofar … knock, knock.. (knocking on wood), we haven't seen the problem of not being able to search in the System Editor (W2k SP 2 plus OI 3.74 with NT Services).

Now are you able to get procedures over 50K under Windows 2000. You are running Windows 2000 right. If so, this is encouraging. Are you doing anything special?

{Oystein, excuse me for changing the subject here, but I hope you don't mind )

Ray

Hi Ray

Hmm, I do have big procedures, the longest is around 56K. I don't get infinite length. The way I do it, is when things start crapping out, I close everything down and shutdown, count to ten, restart. This maximises available system memory. I make sure as few things are automatically started on boot up/log in as possible. No outlook or lotus or anything else.

BTW I'm using Win95 to develop, on a 128MB Ram PC. We are just starting to experiment with Win2000, for running the system. I'm hoping for an upgraded NLM first.

So now I have the cleanest PC memory I can manage, I start up my OI App. Then I go into system editor, open up my proc, do edit | select all; edit | Copy then paste the code into a new text document using Notepad and save it (I'm a little bit paranoid about system crashes). Once it is saved (backed up) to my satisfaction, I return to system editor, cut the code and save the proc empty! Then I go back to notepad, edit select all again on the backup text, and paste it back into the proc and save it (and compile it).

Note if the proc goes weird when I first open it, I cancel so as not to update the proc with weirdness. (shutdown/10/restart) Then I use copy_row_to_os (with conversion) to get the thing out to text. then (after checking the text file is complete) clear out the original proc, save and paste the text back in…

As long as I am on a reasonably fresh startup, I can get a fair bit of code jammed in. This is with OI 3.7 and Oengine 3.7 - I think Oystein is still using an old OI as well. I have an older app on an older OI 3.3 I think and it is harder to jam stuff into it but the same technique works. Usually I split stuff around the 35K mark though. Especially reports.

So that is why I'm thinking Oystein's problem might be fixed by reboot, since he's sure it isn't the mouse wheel driver problem (which seems to be fixed with OI 3.7.4 - nice)

Scott

Proc in boots.

boot skoot'n proc

restart is not enough

Its interesting how you say that the memory slowly gets chewed up while running 95 and you eventually have to re-boot. I used to have that problem before I went onto 2000. I found one of the major causes of the memory being chewed up was using large common variables. Even using the FREECOMMON statement didn't reallocate the memory. I found a stopgap solution of using a suggestion from an earlier discussion. A product called MEMTURBO (I think) or something like that. Do a search for MEMTURBO in the OI discussion section. This made the system much more stable. Removing the huge common arrays almost completely cured the wierd problems I was having. Moving onto 2000 pretty well stops the memory problems but creates other problems that create minor annoyances. One good thing about it though is that if you set up the icon properties for OI to "Run In Separate Memory Space" then when you have to ctrl-alt-del or stall open engine by letting the clutch out too quickly, you can re-launch OI without getting OI boot up f

ailure.

As for large programs. The largest is just over 50000 bytes, (1800 lines) created with system editor and the search function works ok.

View this thread on the forum...