REFRESHLIST is only a property of the list type controls like listviews and comboboxes. That is why you are getting the error.
It would be better form, and more robust as R:BASE matures, to use PROPERTY to update the TEXTVALUE or CAPION of the control displaying your value. R:Docs will let you find the correct property for any given control. Dennis McGrath > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of John > Docherty > Sent: Wednesday, February 11, 2015 2:49 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: Property Refreshlist errors > > Razzak, > > Thanks for that. I too have had some property 'errors' recently in code that > has 'worked' for years so I will check my spelling etc. and use the > CHECKPROP option. > > Regards, > > John Docherty > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of A. > Razzak > Memon > Sent: Thursday, 12 February 2015 8:57 a.m. > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: Property Refreshlist errors > > At 12:45 PM 2/11/2015, Tom Frederick wrote: > > >Suddenly errors for property commands are popping up, which we have > >never had. > >vZRisk is an integer count of how many Risks exist for ZID, then the > >Refreshlist changes the total on the screen. Has always worked. Still > >does, but it also now brings up this error message. > > > >COMPUTE vZRisk AS COUNT ZID FROM Z_Risks_Info WHERE ZID = .vZID > >PROPERTY vZRisk RefreshList 'True' > > > >-error- Property 'Refreshlist' not found in component 'vZRisk' or > >assigned value is invalid. > > > >This now happens for every Property Refreshlist in the database at > >work. This started about 3 days ago. Did reload and rebuild. No changes > >to CONFIG that I remember. This happens in compiled and non-compiled > >versions. Using > >1/9 update. > >No findable virus. Stumped for cause and solution. Next step erase > >R:Base, reload from disk and apply update. > > > Tom, > > FWIW ... > > 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. >
