I tried this but  UINOTIF does not stay off
As soon as I create an index on a temp table it gets set to ON

Dennis McGrath
Software Developer
QMI Security Solutions
1661 Glenlake Ave
Itasca IL 60143
630-980-8461
dmcgr...@qmiusa.com

-----Original Message-----
From: rbase-l@rbase.com [mailto:rbase-l@rbase.com] On Behalf Of A. Razzak Memon
Sent: Thursday, November 07, 2013 1:03 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: compiled apps best practice

At 12:59 AM 11/7/2013, Javier Valencia wrote:

>Thanks R:azzak,
>I took it for a drive and looks good. I have a couple of questions, why do
>you have the these two commands?
>
>SET UINOTIF OFF
>What is the purpose of this command? Is it used  only for performance?
>
>PROPERTY APPLICATION FLUSHMEM 'TRUE'
>Where is the best way to place this command and how often can it be used?
>Is there a performance penalty using it often and at different places in
>a compiled application?


Javier,

The sample application is designed and intended to illustrate the use of
R:BASE External Form File (.rff) to manage the entire application flow
in a multi-user environment, especially when using the R:Compiler 9.5.

To answer your questions ...

Technically, "SET UINOTIF OFF/ON" controls the automatic user interface
notifications/updates for Database Explorer to refresh the list and al
details regarding Tables, Views, Stored Procedures, Forms, Reports,
Labels, External Forms, Applications, and Command Files.

In a typical R:Compiled application environment when there is no Database
Explorer, no RBDefine, and no Form/Label/Report Designers, the use of
"SET UINOTIF OFF" disables all callbacks that are constantly being sent
to front-end when any updates are performed to refresh the DB Explorer.
Thus, a MAJOR improvement in performance. The on-demand use of CONNect
and DISConnect database(s) is also fast in such environment.

Depending on your application, you will have to find the best place to
use the PROPERTY APPLICATION FLUSHMEM 'TRUE' command.

Typically, after manipulating large BLOB data, heavy SORT by very large
Reports, creating and saving heavy duty PDF reports with Rich Text and
BLOB data, Forms, and Custom Plugins would be the perfect place to use
the "FLUSHMEM" command.

Using the "FLUSHMEM" right after SDETACHing and SDISCONNECTing foreign
database(s) is also a perfect spot.

Implemented a long time ago (as undocumented commands), these special
SETtings and PROPERTY commands are a result of designing and deploying
very complex applications for our Government & Corporate clients using
R:BASE eXtreme 9.5 (64) along with custom R:BASE Interfaces & Plugins.

Have fun and make sure to explore all details in that sample application!

Very Best R:egards,

Razzak.

www.rbase.com
www.facebook.com/rbase
-- 
30+ years of continuous innovation!
15 Years of R:BASE Technologies, Inc. making R:BASE what it is today!
-- 


Reply via email to