I was trying to troubleshoot some SQL statments. I counldn't figure out
what's going on until when I looked closely to the index name with a space
at the end.
There was no way for me to know whether or not the index name had a space at
the end. I had to reverse engineer the table.

See my queries:
CREATE INDEX IF NOT EXISTS "Businessdate_IDX" ON "ParentGameIncomeItems"
("BusinessDate" DESC); and
CREATE INDEX IF NOT EXISTS "Businessdate_IDX " ON "ParentGameIncomeItems"
("BusinessDate" DESC);

The 1st query gave me the error message: DBISAM Engine error # 10027 the
secondary index 'Businessdate_IDX' already exists for the table
"ParentGameIncomeItems".
which is not correct. My table did have a secondary index but it was called
"Businessdate_IDX "  with an extra space at the end.
I think this is odd, I am not sure if it was reported earlier. I just wanted
to make sure we are on the same page.

Thank you,
-Halim

Halim,

<< I think this is odd, I am not sure if it was reported earlier. I just
wanted to make sure we are on the same page. >>

Is this DBISAM that you're referring to ?  The reason that I ask is that
this is the ElevateDB SQL newsgroup.

--
Tim Young
Elevate Software
www.elevatesoft.com

Sorry,  This was a DBISAM issue.
-Halim
"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:AF60A323-58F6-4BF5-9950-FE5330D4B744@news.elevatesoft.com...
> Halim,
>
> << I think this is odd, I am not sure if it was reported earlier. I just
> wanted to make sure we are on the same page. >>
>
> Is this DBISAM that you're referring to ?  The reason that I ask is that
> this is the ElevateDB SQL newsgroup.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>