Quirky Editor & disappearing records (OpenInsight Specific)
At 20 JUN 2001 01:57:33AM rayc@symmetryinfo.com wrote:
To all,
I think I've seen this before, but I would appreciate some verification on this quirky problem with the System Editor. I noticed in the past that when I load a relatively large SP into it that the record may not display or if you do load it in that the next time you try to bring it up that it will be gone (blank).
For example, just a few minutes ago, I wanted to look at MDI frame in SYSREPOSWINS because of some problem I was having. I saw that it was 38K or so. The next time I wanted to look at it in the form designer I only saw a "blank" MDI frame. However if I ran the frame from Application Manager, I could see the correct MDI frame. Fortunately, I was able to copy the MDI frame from a backup copy on my hard drive.
Is this the normal behavior of the System Editor Edit box. That is, if you load it with large record (GT 32K) that you may lose it??
Thanks.
Ray Chan
rayc@symmetryinfo.com
onmouseover=window.status=imagine … ;return(true)"
Ray Chan ~ Symmetry Info
At 20 JUN 2001 11:33AM Donald Bakke wrote:
Ray,
We've seen the editor refuse to display text when the record is very large or if a Char(0) somehow got inserted into the record. A quick use of AREV's editor told us that the information was still instact. Sometimes it seems to be a resource issue so a restart resolves the problem for a while.
The typical odd behavour of the editor is that the last few lines of our larger programs get truncated with odd characters. The program still compiles, however, so it only appears to be a visual anomoly and doesn't affect the actual code.
dbakke@srpcs.com
At 20 JUN 2001 12:32PM rayc@symmetryinfo.com wrote:
Don,
Thanks for your reply. I just thought of something. With regards to stored procedures and the system editor, could I get around the editor's limitation by doing my editing in an external editor, e.g., NoteTab, and then do a Copy_OS_to_Row to SYSPROCS and then compile the program via Recompile_Proc.
If this cumbersome process works, then it would save me time in having to "cut" up my AREV programs . Of course, if you (or anyone else) ever come up with a neat editor utility that works within OI and doesn't have the 32K limitation, it could save developers time and I'm sure that people would pay for it. Maybe RTI would consider offering this to people in the Works program!
FYI, the record that got lost was the MDI frame (FRW_MAIN). When I brought it up in form designer nothin showed up except some naked looking MDI frame. This happened after I used the system editor to look at it (38K). Fortunately, I had a backup copy somewhere and was able to recover. No more using system editor to look at this 'puppy'.
Thanks again,
Ray
rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"
Ray Chan ~ Symmetry Info
At 20 JUN 2001 04:34PM Robert Lee wrote:
Ray
I wonder whether your disappearing menu isn't related to your subsequent post about your very large menu. When we were struggling with our largest menu, it would disappear on us occationally just as you described (goes naked, but you can look at it in the System Editor and everything seems intact). That's what finally forced us to break up the menu into lots of little ones and we haven't had a problem since.
Although I didn't think of it at the time, you could try deleting out a few menu items and see if the menu 'magically returns'. I have reason to suspect it might…
Using smaller menu names, as was mentioned in a thread you started a week or two ago, also helps.
Robert
At 25 JUN 2001 10:08PM Scott, LMS wrote:
Hi Ray
My workarounds for the editor when things start getting weird
1. exit without saving if things have disappeared - I have found if I save a "disappeared" thing, it stays disappeared. Mostly this applies to bound edit tables not being able to fit everything, truncating what it can't fit and then saving the truncated record, argh.
2. Close out of OI, and reboot to get a fresh "memory". Do not open anything that might cause memory leakage eg outlook or word or IE.
3. Open up OI and system editor and the procedure I was trying to edit
Stuff is usually there unless I did a save while operating "blind". make a backup at this point Then I do Edit Select All, Edit Cut !, save, then Edit Paste, save.
This seems to get rid of any funny characters that were in the record and also gives you a few thousand characters more leeway in your procedure. Only edit this procedure when you are sure you have all your RAM and no memory leak wastage. Usually I look for ways of breaking things up at this point, because breaking it up is better than losing it.
I haven't had the naked form problem, but I have had to clean out a few menus, especially removing the commented out menu options, so that the complete menus were available.
Scott, LMS