Good Morning lksseven,
Please send your design files (DSR & DDT) to support@lantica.com so that we can help you resolve this issue.

Larry,
We have received your files and we have started looking into your issue.


From what we are seeing in our testing here, you have multiple uses of #Include "sbasic_include.sbas"  throughout your programming. This can cause the compilation time when you first open your application to increase (which may cause Sesame to appear locked up). We found that after 5-7 minutes of compiling your programming the forms finished loading and were usable. Try removing the include statement from all of your programmed events and then add #Include "sbasic_include.sbas" in the Global Code section of your programming. The include statement does not need to appear anywhere else in your programming.

Ben,

I removed #Include "sbasic_include.sbas" from all events and added it to Global Code for each form.

the forms load MUCH faster.

Unfortunately, any code in the ItemQty:nDraw event still makes the Order screen appear to freeze/lockup.  So I /*  */  the code in the OnDraw event screen, reloaded, and the Order screen still was frozen/locked.  So I deleted the OnDraw event altogether, and then everything worked fine.

What do I try next?

Ben,

Good morning!

I used the following code in ItemQty::OnDraw, and it froze/locked - sesame.exe was using 50% of CPU.

SOLines!ItemQty::OnDraw

// if table view (for printing purposes) and ItemQty is a negative number, then
// I want the ItemQty background to be yellow FOR only that line item that is a
// negative number, otherwise I want the background to be white

If (@FormViewType("SOLines") = FORM_VIEW_TYPE_TABLE) and (@ToNumber(ItemQty) < 0)
  {
    RGBColor(ItemQty, -1, -1, -1, 255, 255, 0)
  }

    else
     {
     RGBColor(ItemQty, -1, -1, -1, 255, 255, 255)
     }

Lenovo W700 laptop (2 months old), Intel Core 2 Duo CPU T9400 @ 2.53GHz.
3gb RAM, WinXP Pro, service pak 3.   My 'in operation' Sesame server is also Lenovo Tower, M57model, about 8 months old, 3gb RAM, WinXP Pro, ServPak3.
   
Task Manager shows sesame.exe using anywhere from 33mb to 66mb memory (but it doesn't seem to cannibalize more and more memory, as it was when I had #Include "sbasic_include.sbas" strewn throughout my events like a drunken sailor) , and about 50% of the CPU utilization.  I only let it go for 30 to 45 seconds or so (the time it takes me to walk outside and howl and walk back in again - haha) before killing it with Task manager.

85% breakthrough ....

I was having a nagging issue of several workstations getting sbasic runtime error messages when printing sales orders.  I was starting to suspect that these two users were blowing through the screen so quick that the code wasn't keeping up.  Couple that with your very welcome suggestion that I put #Include "sbasic_include.sbas" only in Global Code (which meant that the app loaded so much quicker) and I got to thinking ... I have Just In Time Compilation set to ON for all of my workstations because the other way was horrendously slow loading the app (due to my ignorance about #Include "sbasic_include.sbas" overuse).  So, with the vastly increased load speeds, I decided to switch off Just In Time Compilation .... I did so this evening before leaving the office (including my laptop), and the runtime errors stopped popping up.

So when I set up just now to follow your directions and let computer run for 5 or 10 minutes to see if it would finally load (having coded an OnDraw event), the app loaded with ease - no lockup, no freeze, no problem!
     So, it seems that OnDraw does not like Just In Time Compilation (at least in my app).

The other 15% yet to go ..... while the app works, the code itself did not - it does not change the background color - in tableview - of ItemQty if ItemQty is a negative number.  Where is my code off?

oki dokie.  Will wait to hear.

While I was waiting, I noticed something bizarre.  I turned off Just In Time Compilation for the above reasons.  But with JIT off, upon clicking Orders (or its subform SOLines) from Application Menu, which presents the 'search/update Orders' tab.  If I hit F10 to find all records, it says 'so results returned from query'.  If I then click 'Clear Search Criteria' from Command Menu on that tab, and then hit F10, it finds all of my records.  But if I then press F7 and enter a specific search criteria (a client id, for example) it says 'no results returned from query'.

     If I change my sesame.ini file back to Just In Time Compilation: ON, then Orders and SOLines performs normally, with an initial F10 returning all of my records, F7 and specific search criteria returning correct results.

The other 6 or 7 databases in this app perform normally in both settings of Just In Time Compilation.  It's only Orders and SOLines (with which I was having the initial issue of OnDraw).

What could I have done to the code (or could it have been something I've done) that would cause Orders and SOLines to act normally with JIT on, but be on the fritz with JIT off ?  
       
Two more observations:
1)  with JIT off, when in SOLines form, I click on Simple Search, leave criteria blank and click Accept.  It finds all my records (now it's in Update mode).  If I go to the last record and then continue to press F10, it just keeps creating new blank records.
       But if JIT is on, and I go to the last record in SOLines form, and press F10, it only allows me to create one blank record.

2)  with JIT off, once I get to the Orders or SOLines form in 'search/update tab, I can't escape that tab by hitting ESC key.  I have to click 'close tab' button on Command menu