I started using the same name for Component and Data field because we use Spell Checker for almost every screen. Our database is very text and note heavy. Example 2 in the SpellCheck95 pdf has Field as ContLName and the CompID as ContLName. EEP is: SET VAR vColumnName = .RBTI_Form_ColName PLUGIN RSpellChecker .vColumnName RETURN
Spellcheck works whenever Field and CompID match. If they do not match, Spellcheck will not work. I stuck with the same Field/CompID matching process since it worked every time. Tom Frederick President/CEO Elm City Center 1314 W Walnut Jacksonville, IL 62650 O-217-245-9504 F-217-245-2350 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bruce A. Chitiea Sent: Wednesday, February 11, 2015 2:36 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Property Refreshlist errors FWIW: May I recommend the practice of naming objects for what they are and how they relate to each other, only one step beyond your existing practice: Table: Heart_t Temp Table: Heart_tt View: Heart_vw Temp View: Heart_tvw ColumnName: HeartID Variable: vHeartID ComponentID: HeartID_cid Speeds visual code scanning dramatically, enables scanning for classes of objects and enhances consistency in coding. At least for me. Bruce -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tom Frederick Sent: Wednesday, February 11, 2015 12:22 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Property Refreshlist errors Mike, I had used the ComponentID and Variable field having the same name many times with no problems until now. It was simply a way to make sure I could easily trace back to where something was used. Never thought much about it because it has worked for years and variables get cleared as soon as they are no longer needed. Tom Frederick President/CEO Elm City Center 1314 W Walnut Jacksonville, IL 62650 O-217-245-9504 F-217-245-2350 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of MikeB Sent: Wednesday, February 11, 2015 12:09 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Property Refreshlist errors Why is the Variable vZRisk the same name as the ComponentId of the object? You could imagine that this might cause a problem in the way RBase reduces things it keeps track of to tokens. Guessing from the capitalization in your post that these were actual Cut and Paste and not mistyped.... > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Tom > Frederick > Sent: Wednesday, February 11, 2015 12:46 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Property Refreshlist errors > > 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 Frederick > President/CEO > Elm City Center > 1314 W Walnut > Jacksonville, IL 62650 > O-217-245-9504 > F-217-245-2350 > [email protected]<mailto:[email protected]>
