GMOcreator Posted November 12, 2001 Posted November 12, 2001 (This is related to my previous post on trying to fire a script upon entering a field) This was my new idea to solve the bind I'm in: I've created a script that fires after any of my 20+ fields are modified. The Script works accept this status flag: status(CurrentFieldName). I want to create if/then commands in the script that does this: If ["Status(CurrentFieldName) = "BLAH""] Set Field ["gHistory", "History"] Set Field ["History", & "gHistory & ... so and so changed BLAH from 'this' to 'that'...] Exit Script End If If ["Status(CurrentFieldName) = "JUNK""]... ... Essentially, it would page through 20+ if/thens until the status flag hits on the right field name, and would then update the History field. However, the status flag doesn't seem to work through the plugin. Perhaps because the "virtual cursor" leaves that field and moves on through the plugin somewhere??? Who knows... Any suggestions/ideas? Thanks
mdpres Posted November 27, 2001 Posted November 27, 2001 quote: Originally posted by GMOcreator: (This is related to my previous post on trying to fire a script upon entering a field) This was my new idea to solve the bind I'm in: I've created a script that fires after any of my 20+ fields are modified. The Script works accept this status flag: status(CurrentFieldName). I want to create if/then commands in the script that does this: If ["Status(CurrentFieldName) = "BLAH""] Set Field ["gHistory", "History"] Set Field ["History", & "gHistory & ... so and so changed BLAH from 'this' to 'that'...] Exit Script End If If ["Status(CurrentFieldName) = "JUNK""]... ... Essentially, it would page through 20+ if/thens until the status flag hits on the right field name, and would then update the History field. However, the status flag doesn't seem to work through the plugin. Perhaps because the "virtual cursor" leaves that field and moves on through the plugin somewhere??? Who knows... Any suggestions/ideas? Thanks Is blah the name of the field "Status(CurrentFieldName" returns the name of the field not the data entered into it. if your field data is blah then blah = blah set field etc. Dean
SteveB Posted November 28, 2001 Posted November 28, 2001 I believe this is one of the longstanding problems/bugs, with no real solution. This function does not work under most (if not all) conditions.
Recommended Posts
This topic is 8740 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now