UX xbasic doesn't like ==

[Peter.Greulich]

== is valid xbasic.

In the Code Editor:

? "a" == "A"
= .F.


? "A" == "A"
= .T.

But if I try that in an xbasic callback, she chokes.

I need to do a case comparison. Guess I'll find another way.

[-Jinx-]

Re: UX xbasic doesn't like ==

Works in a UX for me, in an ajax callback; when it's dimmed anyway.

function TestCase as c (e as p)

dim jscmd as c

dim t1 as c = "A"

	if t1 == "a" then
		jscmd = "alert('lowercase');"
	else if t1 == "A" then
		jscmd = "alert('uppercase');"
	end if
	
testCase = jscmd

end function

[Peter.Greulich]

Re: UX xbasic doesn't like ==

Dimming it gets rid of the error message, but it won't process my code in the UX

= works, == doesn't.

[-Jinx-]

Re: UX xbasic doesn't like ==

Can you give an example of what you're doing? In my example, changing this line: dim t1 as c = "A" to dim t1 as c = "a" will give the correct "lowercase" alert so it seems to be working just fine. This is being called by a button with an ajax callback inside the click event.

Maybe there is something else in your code it doesn't like.

[-Jinx-]

Re: UX xbasic doesn't like ==

Even though I'm not sure why the above doesn't work for you when it seems fine for me, here's more food for thought. You can test the ascii value to know if it's an upper or lower case letter.

function TestCase as c (e as p)
dim jscmd as c
dim txtcs as c
dim fld as c = e.dataSubmitted.FIELD1

dim tst as n = ASC(fld)

if tst >= 97 .AND. tst <= 122 then
	txtcs = "lowercase"
	else if tst >= 65 .AND. tst <= 90 then
	txtcs = "UPPERCASE"
	else
	txtcs = "Not a Letter"
end if

jscmd = "alert('"+txtcs+"');"
	
TestCase = jscmd

end function

[Peter.Greulich]

Re: UX xbasic doesn't like ==

Good idea.

[Peter.Greulich]

Re: UX xbasic doesn't like ==

Solved it using alltrim(). Beginners mistake.

[Al Buchholz]

Re: UX xbasic doesn't like ==

Solved it using alltrim(). Beginners mistake.

So the actual code that you are using is not the example that you showed?

Can you provide a before and after look for the next guy that finds this?

[Peter.Greulich]

Re: UX xbasic doesn't like ==

Here's the relevant code that does not work :

function xbLogin as c (e as p)
...
If vPassword == vUserPwd .AND. vUserSerial = vMobSerial
...

Here's the relevant code that does work :

function xbLogin as c (e as p)
Dim vUserPwd as C
Dim vPassword as C
...
If alltrim(vPassword) == alltrim(vUserPwd) .AND. vUserSerial = vMobSerial
...

Note: for reasons I will not get into here, this app requires customized login code and does not use Alpha security.

[Al Buchholz]

Re: UX xbasic doesn't like ==

Here's the relevant code that does not work :

function xbLogin as c (e as p)
...
If vPassword == vUserPwd .AND. vUserSerial = vMobSerial
...

Here's the relevant code that does work :

function xbLogin as c (e as p)
Dim vUserPwd as C
Dim vPassword as C
...
If alltrim(vPassword) == alltrim(vUserPwd) .AND. vUserSerial = vMobSerial
...

Note: for reasons I will not get into here, this app requires customized login code and does not use Alpha security.

To confirm, it requires both the dim and the alltrim() to work, or merely the alltrim().

[Peter.Greulich]

Re: UX xbasic doesn't like ==

Hhmm... yesterday it requires both. Now I just removed the DIM and it still works - no errors. So I guess the dim is optional. Something else must have been going on when I got the error message w/o the dim. But I'll keep the dim on general principles.

[GGandhi]

Re: UX xbasic doesn't like ==

this is not really a question may be, but just curious..
the code in post #1 and in post #9 are vastly different,
Why?

[Peter.Greulich]

Re: UX xbasic doesn't like ==

In #1 I was demonstrating == vs =, just in case someone was unclear on the basic functionality. My problem was compounded because Alpha was giving me error messages in the UX doing the same thing. Today no error messages.

[GGandhi]

Re: UX xbasic doesn't like ==

http://wiki.alphasoftware.com/~alpha...ching+Operator

Somebody would have pointed out this page to you, you would have found the answer earlier and moved on.

[Peter.Greulich]

Re: UX xbasic doesn't like ==

Gandhi, I have know the difference between = and == for over 20 years. Thanks.
If you read the thread - esp. post #1 you will see that the problem was the UX choking yesterday and an oversight on my part not using alltrim().