One limitation though is from testing, the CAPTION string in RBase forms 
is limited to 1023 characters.  Windows forms can hold more than a 100K.  
  1023 Chars is still a fair amount, but If one were to desire to pass 
more, it would likely have to be via a write to disk and subsequent 
retrieval and execution.  I guess I am kind of writing and thinking in 
terms of passing "actual" object names, Propertes and values at runtime, 
which if lengthy could consume a fair patch of 1K.



On Tuesday, October 30, 2018 at 3:46:24 PM UTC-4, crobbins wrote:
>
> Thanks Mike. I can’t wait to tear into it!  You’ve totally awoken my 
> curiosity.  
>
> Claudine 
>
> Sent from my iPhone
>
> On Oct 29, 2018, at 9:56 PM, Michael Byerley <[email protected] 
> <javascript:>> wrote:
>
>
>
> Go ahead and download the RBase Calendar from Here: 
>
> http://byerley.net/(S(syqysn45jp2uc3quom5gtl2t))/Download_A/RbCalendar.zip
>
> 1.  Load the calendar into a non production database.  You may find it 
> useful :)
> 2.  Read the comments in the CalDemo.rmd file to see the valuelist that is 
> passed in the Caption String.
> 3.  Look at the OnAfterStart EEP to see how the string is parsed, 
> utilizing the values passed.
>
> Now taking a cue from that process, you could take a step further and make 
> each element of the string and instead of passing just a value to be used, 
> you could put Name / Value pairs in the following fashion:
>
> EDIT USING rbcalendar CAPTION 
> 'FormWidth=180,FormHeight=500,FormColor=red,ReturnVarName=,vRetDate,'
>
> Then modify slightly the parsing method I used to a Switch/Endsw that 
> could track to the NAME half of the name value pairs passed, with the VALUE 
> half being consumed appropriately by PROPERTY, GETPROPERTY, or direct usage 
> as a var.
>
>  
>
> On Monday, October 29, 2018 at 1:10:55 PM UTC-4, crobbins wrote: 
>>
>> Thank you Mike.  I’ve already included your form in an SP and understand 
>> the passing of parameters.  I also understand property commands located 
>> immediately after calling the SP.  However, using the CAPTION string for 
>> anything more than cosmetics escapes me.
>>
>>  
>>
>> Claudine
>>
>>  
>>
>> *From:* [email protected] [mailto:[email protected]] *On 
>> Behalf Of *Michael Byerley
>> *Sent:* Sunday, October 28, 2018 12:47 PM
>> *To:* RBASE-L
>> *Subject:* Re: [RBASE-L] - LISTOF question 10.0.4.10913
>>
>>  
>>
>>  
>>
>>  
>>
>>   One further comment on this.  You can blackbox the form solution in a 
>> couple of ways, one being to put the form inside of a stored procedure so 
>> you can call it from there,
>>
>> then using property commands to change the table name and colum spec for 
>> the listbox, or simply utilize the CAPTION string that is the argument of 
>> Edit Using or Enter Using to contain an argument of the elements you want 
>> to change in the onAfter start of the form.
>>
>>  
>>
>>   If you have ever used my RBase form based Calendar, you will see its' 
>> procedure there.
>>
>>  
>>
>>   So by doing that, you could change the properties of the pseudo Choose 
>> box on the fly, and reuse it anytime the need arises in lieu of having a 
>> separate form for each problem.
>>
>>  
>>
>>   Over the course of time since the humble 7.0, RBase has provided many 
>> pathways to problem solution and when there is none apparent, there is 
>> always a reasonably willing RDCC..  :)
>>
>>  
>>
>>
>>
>> On Saturday, October 27, 2018 at 10:53:57 PM UTC-4, javier.valencia wrote:
>>
>> Claudine,
>>
>>  
>>
>> Try the following:
>>
>>  
>>
>> SELECT LISTOF('''' +  your column + '''') into xxx from your_table WHERE …
>>
>>  
>>
>> All the items should have single quotes and the comma should be inside 
>> the quotes.
>>
>>  
>>
>> Javier,
>>
>>  
>>
>> Javier Valencia, PE
>>
>> O: 913-829-0888
>>
>> H: 913-397-9605
>>
>> C: 913-915-3137
>>
>>  
>>
>> *From:* [email protected] [mailto:[email protected]] *On 
>> Behalf Of *Claudine Robbins
>> *Sent:* Friday, October 26, 2018 3:08 PM
>> *To:* [email protected]
>> *Subject:* [RBASE-L] - LISTOF question 10.0.4.10913
>>
>>  
>>
>> Hello all,
>>
>>  
>>
>> My experience with LISTOF is that it automatically puts quotes around 
>> fields that contain commas but I’m running into a situation where it does 
>> not.
>>
>>  
>>
>> One of the fields is YELLOW JACKET CONSTRUCTION, INC., LISTOF returns the 
>> space plus INC. as a separate value.  
>>
>>  
>>
>> However, it correctly returns 3 for the ITEMCNT variable.
>>
>>  
>>
>> What am I overlooking?
>>
>>  
>>
>> R>sho v vValueList
>>
>> YELLOW JACKET CONSTRUCTION, 
>>
>> INC.,YELLOW JACKET 
>>
>> OILFIELD,YELLOWHOUSE 
>>
>> MACHINERY CO.
>>
>>  
>>
>> [image: cid:[email protected]]
>>
>> -- 
>> For group guidelines, visit 
>> http://www.rbase.com/support/usersgroup_guidelines.php
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "RBASE-L" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>> -- 
>> For group guidelines, visit 
>> http://www.rbase.com/support/usersgroup_guidelines.php
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "RBASE-L" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> For group guidelines, visit 
> http://www.rbase.com/support/usersgroup_guidelines.php
> --- 
> You received this message because you are subscribed to the Google Groups 
> "RBASE-L" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
--- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to