Greetings, BTW... I did not want to give the impression that:
F("Next Row") = 0 would work...
It may be you'll need to do this evaluation in a sub routine as opposed to a
Rule.
Regards,
Thom
Thom C. Blackwell
Product Manager
Boston Software Systems
(866) 653-5105 ex 807
www.bossoft.com <http://www.bossoft.com/>
Sign up for my weekly webinar!
<http://www.bostonworkstation.com/customer_center/special_events.aspx>
LEGAL NOTICE Unless expressly stated otherwise, this message is confidential
and may be privileged. It is intended for the addressee(s) only. Access to this
E-mail by anyone else is unauthorized. If you are not an addressee, any
disclosure or copying of the contents of this E-mail or any action taken (or
not taken) in reliance on it is unauthorized and may be unlawful. If you are
not an addressee, please inform the sender immediately, then delete this
message and empty from your trash.
From: [email protected] [mailto:[email protected]]
Sent: Wednesday, March 17, 2010 12:26 PM
To: Talk
Subject: RE: [talkbws] Checking for "non rules" in a rules script
Greetings,
The issue here is that the Rules UI can only build Rule commands using static
text it does not know how to build something that evaluates a property such as
Row.
I have an incomplete picture of what needs done - so the below may just be
interesting but not helpful.
There is a static value that "means" Row - the Row property returns the
current row you are on, and in a condition- you can use 0 to indicate current
row (can use 0 for a column to indicate current column.
This works for the existence of text as well"
t...@0,15 says the text is on the same row as the cursor and starts at column
15
Regards,
Thom
Thom C. Blackwell
Product Manager
Boston Software Systems
(866) 653-5105 ex 807
www.bossoft.com <http://www.bossoft.com/>
Sign up for my weekly webinar!
<http://www.bostonworkstation.com/customer_center/special_events.aspx>
LEGAL NOTICE Unless expressly stated otherwise, this message is confidential
and may be privileged. It is intended for the addressee(s) only. Access to this
E-mail by anyone else is unauthorized. If you are not an addressee, any
disclosure or copying of the contents of this E-mail or any action taken (or
not taken) in reliance on it is unauthorized and may be unlawful. If you are
not an addressee, please inform the sender immediately, then delete this
message and empty from your trash.
From: [email protected] [mailto:[email protected]]
Sent: Wednesday, March 17, 2010 11:44 AM
To: Talk
Subject: [talkbws] Checking for "non rules" in a rules script
If I place the following statement in the Data box:
F("Next Row") = Row
and then right click a step and tell it to "Insert Rule with Condition..." >>>
"When it is true that: F("Next Row") = Row"
It inserts the following (with an action of Key "{F6}"):
F("Next Row") = Row...Key "{F6}"
However, the rule never actually fires.
If I break the script run when I know that the condition is true and go to the
immediate box I get the following:
? F("Next Row") = Row
True
? Rule("F(""Next Row"") = Row")
False
So...What is the trick to get this working?
Thank you,
Mitch Lawrence
Lead Applications Analyst
Enterprise Data Standards - NPR/Automation
CHRISTUS Information Management
: [email protected]
<mailto:[email protected]>
--- To post a message to this list, send mail to: [email protected] You are
currently subscribed as: [email protected] Unsubscribe in the
customer center on our website:
http://www.bostonworkstation.com/customer_center/virtual_user_group_talk.aspx
--- To post a message to this list, send mail to: [email protected] You are
currently subscribed as: [email protected] Unsubscribe in the
customer center on our website:
http://www.bostonworkstation.com/customer_center/virtual_user_group_talk.aspx
--- To post a message to this list, send mail to: [email protected] You are
currently subscribed as: [email protected] Unsubscribe in the
customer center on our website:
http://www.bostonworkstation.com/customer_center/virtual_user_group_talk.aspx <<image001.jpg>>
