ls_new_string = "You were allocated the following agencies:" +
ls_ag_allocated + &
"You were successfully able to unlock for : " + string( ls_allowon) +
&
"You were unable to unlock for: " + string(ls_notallowon)
Messagebox("Unlock My RISER Account",ls_new_string, Information!)
ls_new_string = "You were allocated the following agencies:" +
ls_ag_allocated + &
"~r~nYou were successfully able to unlock for : " + string( ls_allowon) +
&
~r~n"You were unable to unlock for: " + string(ls_notallowon)
--
Terry Dykstra (TeamSybase)
http://powerbuilder.codeXchange.sybase.com/
http://casexpress.sybase.com
product enhancement requests:
http://my.isug.com/cgi-bin/1/c/submit_enhancement
"harlibra" <harl...@yahoo.com> wrote in message
news:126bdf07-8e5c-43ce...@o28g2000yqh.googlegroups.com...
ls_new_string = "You were allocated the following agencies:~r~n" +
ls_ag_allocated + &
"You were successfully able to unlock for : ~r~n" + string( ls_allowon) +
&
"You were unable to unlock for: " + string(ls_notallowon)
-----------------------------------
My Web 2.0 Stuff
Blog: http://bruce.pbdjmagazine.com/
Facebook: http://www.facebook.com/people/Bruce-Armstrong/1600223798
Fotki: http://public.fotki.com/brucearmstrong/
LinkedIn: http://www.linkedin.com/in/bruceaarmstrong
Twitter: http://twitter.com/bruce_armstrong
YouTube: http://www.youtube.com/user/brucearmstrong
For example ( and this is off the top of my head, so may be a few
syntax errors ):
create a non-visual object called n_msg_attrib
Give it two instance variables: string is_allowon, is_notallowon
create a window called w_msg_agencies ( or whatever ) and make it a
response window
Give it three single line edits spaced where you want them, and an OK
button
In the open event, code the following:
n_msg_attrib ln_msg_attrib
ln_msg_attrib = create n_msg_attrib
ln_msg_attrib = Message.PowerObjectParm
sle_1.text = "You were allocated the following agencies:"
sle_2.text = "You were successfully able to unlock for : " +
ln_msg_attrib.is_allowon
sle_3.text = "You were unable to unlock for: " +
ln_msg_attrib.is_notallowon
Destroy ln_msg_attrib
For the Clicked event of the Ok button add:
Close( w_msg_agencies )
In your script that was calling the messagebox, change the logic to:
n_msg_attrib ln_msg_attrib
ln_msg_attrib = create n_msg_attrib
ln_msg_attrib.is_allowon = string( ls_allowon)
ln_msg_attrib.is_notallowon = string( ls_notallowon )
OpenWithParm( w_msg_agencies, ln_msg_attrib )
destroy ln_msg_attrib
--
Terry Dykstra (TeamSybase)
http://powerbuilder.codeXchange.sybase.com/
http://casexpress.sybase.com
product enhancement requests:
http://my.isug.com/cgi-bin/1/c/submit_enhancement
"Bruce Armstrong" <NOCANSPAM_br...@yahoo.com> wrote in message
news:77o0m55f2sf1s9kfl...@4ax.com...
--
Regards ... Chris
ISUG - Communications Director
http://chrispollach.pbdjmagazine.com
"Bruce Armstrong" <NOCANSPAM_br...@yahoo.com> wrote in message
news:77o0m55f2sf1s9kfl...@4ax.com...
>
http://www.eggheadcafe.com/software/aspnet/32267907/msgbox-width-limit-in-vis.aspx
Vista will tend to break long lines earlier. If you add your own line
breaks and the length of the line you're allowing is longer than when
Vista will break you'll get the Vista break, followed by your own
break in the middle of the next line.
On 27 Jan 2010 10:03:53 -0800, "Terry Dykstra [TeamSybase]"
<tddy...@forestoil.ca> wrote:
>Mess up in what way? Can you show a picture of an XP versus Vista/W7
>Messagebox PB formatted messagebox?
On 27 Jan 2010 21:20:04 -0800, "Chris Pollach"
<cpol...@travel-net.com> wrote:
>FWIW: The "~r~n" works the same for me on W7 (PB versions 11.2 through
>12.NET)