Piotr Posted December 16, 2004 Share Posted December 16, 2004 FM7 has a SERIOUS bug that renders all my solutions created in previous versions unusable. I rely heavily on calculations that use statements such as: Case (Field1>0;"something";"something else") or Case (Field1=0;"something";"something else") These Boolean statements no longer work in FM7. Previous versions of FM understood the statement Link to comment Share on other sites More sharing options...
Ender Posted December 16, 2004 Share Posted December 16, 2004 Waa Waa. If you had used the isempty() function that was available, you wouldn't have this problem now. Just because some other trick works, doesn't mean it's appropriate. Bite the bullet and fix your calcs. It's really not that hard. Maybe your DDR can help you locate instances of this type of calc. Link to comment Share on other sites More sharing options...
Piotr Posted December 16, 2004 Author Share Posted December 16, 2004 Thank you Ender for your constructive reply. You missed the point completely: the issue is not that I am too lazy to fix my calculations, the issue is that the Boolean statements in FM7 give FALSE results. I am not going to migrate to the new version until this bug is fixed. Link to comment Share on other sites More sharing options...
RalphL Posted December 17, 2004 Share Posted December 17, 2004 Null and zero are different. Null is an empty field, zero is value. If it worked in previous versions of FMP then they were in error. Hope you have fun with Access. Link to comment Share on other sites More sharing options...
Ugo DI LUCA Posted December 17, 2004 Share Posted December 17, 2004 You may have to wait for a while then, unless you take your time and change your calcs. By the way, what you call booleans aren't booleans structures, and you may find that the real boolean not Field1 will work if you unchecked the not evaluate chen empty. Also, text based calcs should be converted to GetAsNumber(Field1) and would work as well as it was before. There were some adjustments, some I don't like neither, but in this case, I won't bet you are on the right track. Link to comment Share on other sites More sharing options...
Piotr Posted December 17, 2004 Author Share Posted December 17, 2004 Hmmm, I always thought that comparison operators that compare two values and return either True or False make a Boolean statement. The only difference in this case is that True = "empty" and False = "not empty". Please correct me if I'm wrong. Link to comment Share on other sites More sharing options...
Oldfogey Posted December 17, 2004 Share Posted December 17, 2004 Piotr, Good luck with Access! Its handling of Empty, Zero, Null and "Who cares" leaves a LOT to be desired. If I were you, I would be having nightmares about the errors in my historical calculations. If you use "Case (Field1>0;"something";"something else")" on a numerical field, it will usually return "something else" if Field1 is empty, in all(?) versions prior to V7 and presumably V7 as well. [Access returns #ERR, I think, or some other of its helpful thingies.] Link to comment Share on other sites More sharing options...
Sxeptomaniac Posted December 17, 2004 Share Posted December 17, 2004 Piotr, I'm not that advanced in Filemaker, but I do know that it is not a bug for FM7 to evaluate Field=0 and isEmpty(field) differently. It's logical. It's easily concievable that a person may want to know when a calculation evaluates to 0, as opposed to when there is no information to calculate. So it's not a bug, just one of those bad habits you picked up early. I've been monitoring these forums to learn how to fix a lot of the bad techniques I used when I was starting. Link to comment Share on other sites More sharing options...
Barbecue Posted December 20, 2004 Share Posted December 20, 2004 All such arguments shall be cast aside when the revolution comes... http://www.thethirdmanifesto.com/ Link to comment Share on other sites More sharing options...
Oldfogey Posted December 22, 2004 Share Posted December 22, 2004 [Let me tell you about my grandchild... ] I expected a pile of twigs, Barbecue. Could the wrong picture be a result of your use of "grandchild..."? Those "..." can play havoc. If I knew how to get a link on this, I'd show you a picture of a REAL grandchild. Link to comment Share on other sites More sharing options...
-Queue- Posted December 22, 2004 Share Posted December 22, 2004 Paul, use [ url=http://www.somesite.com ]click here[ /url ], without the spaces between the brackets and you'll get click here. Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 7086 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