> Hi Rony!
>
> I recommend that you fix the problem long before the SELECT. Start by
> two tables:
>
> CREATE TABLE Test(ID INTEGER, AFIELD VARCHAR(32), CONSTRAINT PK_Test
> (ID) PRIMARY KEY);
>
> CREATE TABLE Test_Integer(ID INTEGER, Test_ID INTEGER, AnInteger
> INTEGER, CONSTRAINT PK_Test_Integer (ID) PRIMARY KEY);
>
> (there may be spelling mistakes, and Test_ID should be a foreign key
> to Test(ID))
>
> Then write an AFTER INSERT OR UPDATE trigger on the Test table that
> simply parses the string and inserts into Test_Integer any number that
> it finds.
>
> HTH,
> Set
Thanks Set,
That would be a good solution if I knew which field to operate on...
unfortunately the one I'm working on is a generic tool: all the tables are
created dynamically, and all the fields MUST be only varchars...
So I think creating an extra table for numerics for each table I create is a
bit too much.
I only wanted to find out whether I could let the users filter records with
this quick way, just in case THEY KNEW that was a numerical field...
It's not important... but thanks a lot anyway!