and just to clarify why I return to the trailing space is due to your response here that you checked your code and with the same results. It's not the code having extra spaces that will cause an issue, it is the spaces at the end in the area where you enter the text object's comp name, that will cause this issue. ----- Original Message ----- From: Jim Belisle To: RBASE-L Mailing List Sent: Wednesday, May 05, 2010 4:41 PM Subject: [RBASE-L] - Re: TEXT TO INTEGER
I have checked out the trailing space theory, completely retyped the code, tried both NINT & INT in the code and still no success. The variable for the total ship days shows in the trace mode but never gets entered into the next var based on the CompID. I think I will rest on this til another day. jim ------------------------------------------------------------------------------ From: [email protected] [mailto:[email protected]] On Behalf Of jan johansen Sent: Wednesday, May 05, 2010 4:07 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: TEXT TO INTEGER Karen, I've had the trailing space bite me a few times so that's why I remembered it. Also in 7.6 I always have to remember things like the 18 character limit. Jan -----Original Message----- From: [email protected] To: [email protected] (RBASE-L Mailing List) Date: Wed, 5 May 2010 16:18:58 EDT Subject: [RBASE-L] - Re: TEXT TO INTEGER Jan: Great point! In RBase forms/reports, if you double-click on a word to copy it while in your eep code, it includes the trailing space. I often write the eep first, then copy and paste the componentid into the proper control. I noticed that if I do not delete that trailing space it seems to "stick" there and doesn't evaluate. Karen Jim, If the first GETPROPERTY is working I would make sure that you have not mis-spelled your DB-Calc with the componentID of Comp_SumSdays. Also look for maybe a trailing space in the componentid of your DB-Calc. Jan
