The other day I imported my Q&A workorder data into my main application, 23,487 records.

It now takes approximately 1 minute for Sesame to open my app.  Is this normal?  I wonder what will happen when I import our 30,618 Invoices.   

Do any of the manuals explain what is happening when the "Loading/Saving" box is doing it's thing?  I assume that the records are being loaded into memory.  What is being saved?

When I move to Client-Server, will this Loading/Saving process occur on the server or the workstation?  I know that each client will need to wait for the programming to compile when a form is opened for the first time, but will they have to Load/Save too?

Quote:

Ah, good.  The reason the "Save" portion is taking a bit of time is that I am, in fact making constant changes in design.  So this should diminish once the app is put into use, as redesign will be less frequent, and record deletions very rare.
Quote:

Excellent news, thank you very much.

Any of the "X" commands will take longer through a slow network, but the first one (which causes the engine to load the external application) will take longer because it must load the app from the file. It is often a good idea to "pre-load" the app before the first XLookup so as to get the delay out of the way before your clients need it.

The ForceRedraw takes place entirely on the client and does not use the net (or the server) at all.

If you have a larger form and call ForceRedraw frequently it can cause flicker. Sesame's window is "double buffered", this means that it is really drawing on a hidden window, and then when the drawing is complete, it copies that window to surface. This, in general, prevents flicker, because the entire window gets refreshed in one fell swoop.

But in the case where ForceRedraw is called frequently and there is a lot to redraw, the ForceRedraw will cause the back buffer to forced to the visible window before the back buffer is complete. That will cause flickering. Always try a routine without the ForceRedraw and make sure it is necessary. And as you design, it is a good idea to comment out ForceRedraws to see if they are all still necessary. Often it is the case that one well placed ForceRedraw can "sum up" several previous calls.

Typically, if you are seeing a lot of flickering, it is due to too many Goto or ThrowFocus statements. Often, if an app is coming from Q&A, Gotos were used to cause programming to run, rather than using subroutines or user defined functions. In Sesame, this can cause a "pinball" effect, as the cursor and chunks of data, are moved around on the screen. In Sesame, Goto and ThrowFocus should only be used to move the cursor (and then only if absolutely necessary and you can think of no other way to help the user), not to cause programming to run.

Of course, in your case, I'm only guessing. There are several things that can cause flicker.

Infinity wrote on Sep 5^th, 2006 at 1:20pm:



If you are client / server, you can use a second client to connect to the server and load the application in question. Or you can merge the "X'd" application into your main application, so it will load when the main app loads.

BOBSCOTT wrote on Sep 5^th, 2006 at 2:55pm:


Yes. And thank you - good sugesstion!