AT() function for cacluated field

[gdcorp]

I am trying to get the at() function to work for calculated field expression - client side Alpha 5 v10.5

substr("abcdef",0,at("c","abcdef")

the starting location 0 is for client side or 1 for desktop apps

should result in "abc" but produces error - it works fine for calculated fields in desktop apps. The substr() works fine as long as the at() is replaced with a N.

I need to be able to extract a substring from the left side up to and including the first occurrence of a specified character.

[gdcorp]

Re: AT() function for cacluated field

Anyone able to help with this problem?

Brad

[Bob Moore]

Re: AT() function for cacluated field

http://www.w3schools.com/jsref/jsref_obj_string.asp

[StephenP]

Re: AT() function for cacluated field

I copied your sample in, and it produced an error. I added ')' to the end, and it worked. Is that your problem?

[Bob Moore]

Re: AT() function for cacluated field

Brad, Sorry I forgot about the "xbasic" like syntax which is allowed for the calculated fields. As a JavaScript programmer, these get me every time and I think this can be really confusing for typical web programmers, trained in JavaScript.

The calculated field allows you to enter JavaScript, to call a user defined JavaScript function that you define in the JavaScript function declarations, which in your case could be a function called calcfield() and its definition could look like :

function calcfield(){
 return $u.s.substr('abcdef',0,(String('abcdef').search(String('c'))+1));
}

Or .. as long as you use the "xbasic" like functions in the expression builder dropdown, Alpha will convert the "xbasic" like expressions to JavaScript when the component is displayed.

So .. you can use either syntax but in the end, it's JavaScript that runs client side in the browser.

[gdcorp]

Re: AT() function for cacluated field

Stephen,

Thanks I forgot to add the ')' when I posted. Although this does work for my example post my search character was '?' which does not work. I could not use chr(63) or chr$(63) for the '?' as this produces an error.

Bob,

Thanks for the javascript option as this will work for the '?' character which was not handled properly by xbasic.