Razzak, as I reintroduce myself into programming and developing with Rbase, I 
am once again astonished by the speed at which boo boo fixes and new tools are 
provided.  We are lucky to have you and rbase!


Sent from my iPad

> On Jan 10, 2015, at 12:59 PM, "A. Razzak Memon" <[email protected]> wrote:
> 
> At 12:32 PM 1/10/2015, Javier Valencia wrote:
> 
>> This is an extremely helpful tool to have when debugging applications.
> 
> You better believe it!
> 
> We will provide you all the intelligence, tools, and gadgets you need
> to deploy the best R:BASE eXtreme 9.5 (32/64) applications out there.
> 
> Very Best R:egards,
> 
> Razzak
> 
> 
>> -----Original Message-----
>> From: [email protected] [mailto:[email protected]] On Behalf Of A. Razzak
>> Memon
>> Sent: Saturday, January 10, 2015 8:00 AM
>> To: RBASE-L Mailing List
>> Subject: [RBASE-L] - Tip of the Day: Using New CHECKPROP Setting
>> 
>> Saturday, January 10, 2015
>> 
>> Tip of the Day: Using New CHECKPROP Setting
>> Product: R:BASE eXtreme 9.5 (32/64)
>> Build..: 9.5.5.20109 or higher
>> www.rupdates.com
>> www.rbaseupdates.com (Mirror Site)
>> Section.: R:BASE Settings
>> Keywords: CHECKPROP
>> 
>> Prior to the official release of R:BASE eXtreme 9.5 (Update 5), any invalid
>> or mistyped PROPERTY/GETPROPERTY "property" keywords were ignored and no
>> validation was performed to identify the invalid "property" value used.
>> 
>> Did you know that PROPERTY and GETPROPERTY command errors can now be
>> displayed if a "property" value is invalid? This enhancement applies to both
>> forms & reports.
>> 
>> Syntax:
>> 
>> SET CHECKPROP ON/OFF
>> 
>> The default value is set to OFF.
>> 
>> A simple example to illustrate the use of this new setting:
>> 
>> Let's say your form On After Start EEP includes the following code:
>> 
>> PROPERTY <ComponentID> VISBLE 'FALSE'
>> RETURN
>> 
>> Notice the misspelled "VISBLE". The valid keyword however is "VISIBLE".
>> 
>> Before, this was ignored and the property keyword was never validated. The
>> users will report this as a bug, because the PROPERTY command doesn't work.
>> Really?
>> 
>> Using the latest Version and Update 5 of R:BASE eXtreme 9.5, Build:
>> 9.5.5.20109:
>> 
>> SET CHECKPROP ON (the DEFAULT is set to OFF)
>> 
>> Now if you run the form with same misspelled property keyword, you will get
>> an
>> -ERROR- Property 'VISBLE' not found in component <ComponentID> or the
>> assigned value is invalid.
>> 
>> This new setting will help you to revisit your code so that you can correct
>> the syntax as well as use a valid property command without wasting valuable
>> time of members of the eXpanded R:Dream Team to debug your forms and
>> reports, etc.
>> 
>> Note:
>> 
>> The errors are only displayed if a new operating condition CHECKPROP is set
>> ON.
>> 
>> (CVAL('CHECKPROP'))
>> Returns the current status of CHECKPROP setting.
>> 
>> SHOW CHECKPROP
>> Displays the current status of CHECKPROP setting.
>> 
>> Very Best R:egards,
>> 
>> Razzak.
>> 
>> www.rbase.com
>> www.facebook.com/rbase
>> --
>> 32 years of continuous innovation!
>> 17 Years of R:BASE Technologies, Inc. making R:BASE what it is today!
>> --
> 
> 


Reply via email to