Division Errors

[Steve1]

Hi All,

I'm having some issues building calculators that call for any type of division because I'm finding that if you save a record and the value for the divisor is set to 0, the software crashes. It even crashes after re-compiling.

I've tried to solve this issue by making the rules for the divisor (an editor) such that you cannot save the record if the value is set to 0 but I can't seem to set the rule appropriately to prevent this.

Any advice would be appreciated, especially if you have successfully built a rule to prevent saving a 0 value to an editor. This would take care of the problem.

I'm not sure if it's appropriate to call this a bug, this seemed like the most appropriate place to post.

Thanks.

-Steve

[TigerSoftware]

Hi All,

I'm having some issues building calculators that call for any type of division because I'm finding that if you save a record and the value for the divisor is set to 0, the software crashes. It even crashes after re-compiling.

I've tried to solve this issue by making the rules for the divisor (an editor) such that you cannot save the record if the value is set to 0 but I can't seem to set the rule appropriately to prevent this.

Any advice would be appreciated, especially if you have successfully built a rule to prevent saving a 0 value to an editor. This would take care of the problem.

I'm not sure if it's appropriate to call this a bug, this seemed like the most appropriate place to post.

Thanks.

-Steve


Steve, it sounds like a bug if it is crashing the software. I will take a look.


Thomas

[Steve1]

Steve, it sounds like a bug if it is crashing the software. I will take a look.


Thomas

Thank you, Thomas. In the meantime, I'm trying to work around this by implementing a rule that says the value of the field must be between 1 and some upper limit. I have checked "save" to enforce the rule when the record is saved but nothing is happening. I would expect an error message or soemthing to come up to let the end user know of the rule. Any guidance on this would be appreciated.

Thanks again.

[TigerSoftware]

Thank you, Thomas. In the meantime, I'm trying to work around this by implementing a rule that says the value of the field must be between 1 and some upper limit. I have checked "save" to enforce the rule when the record is saved but nothing is happening. I would expect an error message or soemthing to come up to let the end user know of the rule. Any guidance on this would be appreciated.

Thanks again.

Steve, the rules are not working like they should. This has been discussed in the forum. I am working on this to rectify it. I will try to get this worked out for the next release which I hope will be very soon. :)

I am trying to get all of these problem fixed quickly. The product launch will be soon and that is when the price increases a lot for a limited amount of people.


Thomas

[Steve1]

Steve, the rules are not working like they should. This has been discussed in the forum. I am working on this to rectify it. I will try to get this worked out for the next release which I hope will be very soon. :)

I am trying to get all of these problem fixed quickly. The product launch will be soon and that is when the price increases a lot for a limited amount of people.


Thomas

Thank you, Thomas. To echo what most everyone in the forum has said, this tool is incredible. I've kicked around a lot of software in the past and you have really come up with something special. I'm also impressed with your responsiveness and patience.

[TigerSoftware]

Thank you, Thomas. To echo what most everyone in the forum has said, this tool is incredible. I've kicked around a lot of software in the past and you have really come up with something special. I'm also impressed with your responsiveness and patience.

Thanks Steve,

I am still working on my patience at times. hehe

The biggest thing for me is to create something that helps people attain their goals. Honestly, I am loving this thing myself. I am a little shocked at how well it turned out and where we are going with this. :)

I like to think of this as the beginning and it is only going to get better, especially with great customers such as yourself and others on this forum.

I am really looking forward to hiring some people to help speed up development including fixing the problems we find.

Thomas

[TigerSoftware]

Steve, can you give me an example of a calculation that is giving you problems. I just worked on trying to create a division error but couldn't get it to error out.


Thanks,


Thomas

[Steve1]

Steve, can you give me an example of a calculation that is giving you problems. I just worked on trying to create a division error but couldn't get it to error out.


Thanks,


Thomas

Hi Thomas,

Sure. Really it's any calculation that includes "0" as the divisor. For example if the calculation is

"Value1 divided by Value2"

and the end user does not enter a value for value2 (making it "0" as far as the software is concerned) that will cause the error. So if Value1 is 1,5, 7, 10 or any number and Value2 is "0", you get that error I described----"Error, division by 0" with a big red X across the screen rendering the application useless, even after re-compiling.

Thanks for jumping on this, Thomas. This is a big one for me.

-Steve

[TigerSoftware]

Hi Thomas,

Sure. Really it's any calculation that includes "0" as the divisor. For example if the calculation is

"Value1 divided by Value2"

and the end user does not enter a value for value2 (making it "0" as far as the software is concerned) that will cause the error. So if Value1 is 1,5, 7, 10 or any number and Value2 is "0", you get that error I described----"Error, division by 0" with a big red X across the screen rendering the application useless, even after re-compiling.

Thanks for jumping on this, Thomas. This is a big one for me.

-Steve

Thanks Steve. That is what I thought you were talking about. I just tried it and didn't get an error. I have the calculated field being set to 0 when there is a problem with the calculation like dividing by 0. Maybe it was the fix I put it.

Anyway, it looks like it is working now and will be in the next update this week.

Now on to rules. :)


Thomas

[Steve1]

Thanks Steve. That is what I thought you were talking about. I just tried it and didn't get an error. I have the calculated field being set to 0 when there is a problem with the calculation like dividing by 0. Maybe it was the fix I put it.

Anyway, it looks like it is working now and will be in the next update this week.

Now on to rules. :)


Thomas

Sweet. Thanks Thomas.