Raybaudi Posted March 23, 2012 Posted March 23, 2012 Based on a bug discovered by Federico Severin bug\'s joke.zip
Ocean West Posted March 23, 2012 Posted March 23, 2012 strange - when i create a new record with new data it evaluates correctly for each?
Raybaudi Posted March 23, 2012 Author Posted March 23, 2012 Because you'll need to fire the script that sets the rep #0
Raybaudi Posted March 23, 2012 Author Posted March 23, 2012 Yes. The bug must be on the unique way to set that repeatition: using the Replace Field Contents [ ] Nor Set Field [ ], neither Set Field by Name [ ], can set that rep.
Raybaudi Posted March 23, 2012 Author Posted March 23, 2012 Continuing to joke, you can set any number of repetition ( 0 or even negative ), but there will always be a single repetition that will occupy the second position in the result of the function List ()
bruceR Posted March 27, 2012 Posted March 27, 2012 Note that this doesn't have to be a repeating field. If you perform a replace on any non-rep field; but use an invalid rep (zero; negative; or emtpy) in your replace operation, you will get a damaged index. Actually you will get an index that holds the new value, but the index shows a question mark. However if you search for record containing the replacement value, you will find them.
Raybaudi Posted March 27, 2012 Author Posted March 27, 2012 This fact supports my hypothesis that the problem is all in that script step.
Recommended Posts
This topic is 4694 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