Iron Speed Technical Forums
Register Latest Topics
 
 
 


Reply
  Author   Comment  
tbfreebird

Registered:
Posts: 27
Reply with quote  #1 
Of the many dropdown lists that i have within my application - almost all have and Indicator (SQL Server Bit Field) that determines if the record is enabled or disabled.

Bute when I try and filter using the Query Wizard/Edit Where Clause from the Design Mode view (Edit Data Sources)... it trows an error within my dropdown control:

ERROR: SYNTAX ERROR: Unexpected Token "="; Expected one of <IDENTIFIER> Line 1; column 26

Ive tried it with every syntax I know - and compared it to static queries direct to database.... they all work, none work through ISD filter...

Is this a known bug?
JimiJ

Avatar / Picture

MVP Developer
Registered:
Posts: 1,927
Reply with quote  #2 
Can you show how you did it that we might be able to offer possible correction or alternative.

Cheers,
Jimi J

__________________

  Jaime Jegonia
[jts_logo]

Iron Speed MVP Developer
 

". . . and whoever sows generously will also reap generously" 2 Cor 9:6

tbfreebird

Registered:
Posts: 27
Reply with quote  #3 
Thanks for you time JimiJ - I'd be happy to provide a screen shot.

Please note that I have tried multiple values:   1 , 0, "0", '0', True, False, etc...

Thanks again for taking a look.

Attached Images
Click image for larger version - Name: FilterDropdown.jpg, Views: 52, Size: 121.13 KB 

rmanzelc

Registered:
Posts: 67
Reply with quote  #4 
Edit: My initial guess, too -- get rid of that = sign in your formula window. IronSpeed handles that for you using the "Operator" dropdown.

We have something very similar, and I use true/false when filtering on my bit's. Just the same as you, they are regarding Inactive/Active for that particular record.

I attached a screenshot for you. You'll notice I used "not equal to" true rather than "equal" to false. This was more an internal issue we had for this record, we had some instances where the inactive flag/bit was blank -- I guess you may want to make sure you don't have any null or blank values in this field in your DB.

Hope that helps you,
RJ


Attached Images
Click image for larger version - Name: Screen_Shot_2013-03-29_at_10.36.30_AM.png, Views: 30, Size: 31.38 KB 

tbfreebird

Registered:
Posts: 27
Reply with quote  #5 
EDIT - THIS SUCCESS WAS SHORT LIVED
-------------------------------------------------------------------------

I should have noted that the "=" sign in my example gets dropped once saved... 

rmanzlec:  Great Response and simple solution!  Your solution worked great!!!  Thanks!!!!!

-------------------------------------------------------------------------
END EDIT - Read on the following posts for more info
tbfreebird

Registered:
Posts: 27
Reply with quote  #6 
Well - my feeling of success was short lived...  I tried a quick test base don the above and it worked...  I was relieved and thought maybe I was simply a dunce that missed something somewhere...

Alas, I patiently went through my entire application - painfully, slowly, using the wizard to update virtually every drop down on every page... until i was done...  Great - now on to some other things...

Later I went to do a quick run through before turning over to test...

Back again : 

ERROR: SYNTAX ERROR: Unexpected Token "="; Expected one of <IDENTIFIER> Line 1; column XX

You have got to be kidding me, right?

Any ideas???
tbfreebird

Registered:
Posts: 27
Reply with quote  #7 

Have been truning over every rock and looking under every bush....

Just happen to decide to walk through every tab and every value:

Formulas, Cell Editor, Data Sources and Code...

As i click around to uncover the values - I find that in the Formulas Tab - the "populate From Value (shows up as Display As) has a duplicated table name... hmmm how did that get there...?

So I fix it and my query now works right...  So I says to myself (thats what I call me:  "myself"):

"hey myself - go check the other drop downs that arent working"...

I do and they are duplicated in the same way.  They should read:

 = TableName.ColumnName

But instead they all have:

= TableName.=TableName.ColumnName

Call me suspicious but this looks like a bug - 'cuz i didnt go around incrorect typing the exact same sequence for 20 different tables with 20 different names...  Im too lazy for that....

So if you run across the error (shows up in the text of your dropdownlist) :  ERROR: SYNTAX ERROR: Unexpected Token "="; Expected one of <IDENTIFIER> Line 1; column

Check the Display As to make sure it didnt get corrupted by something...

BTW - this corrects the original problem as it was never really a problem...  you can use bits (true or false) in the where clause of a dropdownlist...

tbfreebird

Registered:
Posts: 27
Reply with quote  #8 
ALSO - I have determined that this only happens when a sort order is placed on the field that populates the DropDownList... In my case they were is ASC (ascending order).

If I didnt have a sort order and modified the where clause - no corruption.  It only happens if there is a sort.

Note: The same corruption takes place if i remove the sort only (and dont add a where clause).  I have then tested (following removal of the sort) and added a where clause - no corruption...
rmanzelc

Registered:
Posts: 67
Reply with quote  #9 
Sorry to hear of the continued issue. If you do believe it is a bug, I suggest you submit a ticket to IronSpeed with how to re-create it. I haven't run into that issue before, but that's not to say I won't!

RJ
wyldKard

Avatar / Picture

Registered:
Posts: 54
Reply with quote  #10 
Quote:
Originally Posted by tbfreebird
ALSO - I have determined that this only happens when a sort order is placed on the field that populates the DropDownList... In my case they were is ASC (ascending order).

If I didnt have a sort order and modified the where clause - no corruption.  It only happens if there is a sort.

Note: The same corruption takes place if i remove the sort only (and dont add a where clause).  I have then tested (following removal of the sort) and added a where clause - no corruption...


Encountered the same issue today while working on v 12.2.0. I tried removing the ASC part but still the same problem. Was there ever a solution to this after the post from v9.x.x?
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Download Iron Speed Designer

Terms of Service Privacy Statement