Razzak and Dan, Thanks for the info. Never thought of wildcards with Property Commands. Went back and renamed the grouped CompIDs so wild cards would work. Then grouped some notes into one note for the screen. Basically dropped about 85% of the EEP property commands I previously had. It worked the first time it ran. Had one TIME field that caused the drop downs to stop when it was used. Edited it out by grouping two similar data groups together with one time field. What I had worked before, this is much better. Users like the screen change and I like that they have to purposefully turn on a section to put info there. I can see several other places to can use this concept. Next step is the PANEL ideas. I'll get there later tonight after football practice.
Tom Frederick President/CEO Elm City Center 1314 W Walnut Jacksonville, IL 62650 W- 217-245-9504 F - 217-245-2350 E - [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of A. Razzak Memon Sent: Tuesday, October 04, 2011 1:38 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Too many property commands? At 12:42 PM 10/4/2011, Tom Frederick wrote: >I have a screen which tracks contacts with residential homes, >supervisor, RN, family/guardian, and the state. Each section has fields >for who was called, caller, date, time, note, and how they were >contacted. There two drop downs in each section. >Screen total of 42 fields. It works fine. Some users have asked that I >add a check box to control sections of individual fields. >Using COMP ID to enable/disable, refresh, and change field colors as >needed. Each section uses about 28 property commands. >Works great until I put in the 4th section. Then the drop downs stop >working. At this point I am hitting about 100 property commands, so >memory is probably an issue. Is there some way to control a section of >fields with 1-2 property commands. Tried using Enhanced Panels but >those makes the drop downs also stop. >V9.1 with latest updates. Tom, When learning and implementing these cool and powerful features in R:BASE, we all get carried away, because everything works! However, as your application evolves, your users need more, or there is much more to do, you will have to sit back and re-think the whole strategy. Having the positive attitude and appreciation you have for R:BASE, and what R:BASE has done for you and your organization, take a second look at your specific form and find the best way to handle your situation. Here are a few suggestions: 00. There are no limits when assigning component IDs, or using PROPERTY/GETPROPERTY commands. 01. Group all controls with same functions using the same component ID. Yes, you can assign same Component ID to multiple controls. 02. Use the wild card options. This depends on how you have assigned the component IDs. The logic of naming component IDs becomes very important. 03. Place similar controls in a container, such as Panel or Group Box, and then use the PROPERTY command for that Panel or Group Box to manage control properties related to that Panel or Group Box. If you wish to see a demo of such functionality in R:BASE, take a look at the 2011 Annual R:BASE Conference Highlights. http://www.rbase.com/conference/highlights.php Topic: Integrating and Managing Automated Application Security And, here is a preview: http://www.rbase.com/conference/2011_Presentations_Razzak.jpg Good luck! Very Best R:egards, Razzak.
