If I use the following query (where Recno=2)

"SELECT * FROM EstimateData WHERE Recno = ?"

I get the expected response, but if I try

"SELECT * FROM EstimateData WHERE Recno = ? ORDER BY SectionNumber"

The query never returns!

This query works fine in the ElevateDB Manager.

Also I run another query with an order by before this one and it is fine
as well.

I have uploaded a small example project with data into the binaries
newsgroup

Chris Holland

Chris,

<< If I use the following query (where Recno=2)

"SELECT * FROM EstimateData WHERE Recno = ?"

I get the expected response, but if I try

"SELECT * FROM EstimateData WHERE Recno = ? ORDER BY SectionNumber"

The query never returns!

This query works fine in the ElevateDB Manager. >>

Minor item - this is the DBISAM ODBC newsgroup.

Secondly - are you using 1.06 ?  The project that you posted works fine for
me here with 1.06.

--
Tim Young
Elevate Software
www.elevatesoft.com

> Minor item - this is the DBISAM ODBC newsgroup.

Sorry about that, is the correct ElevateDB newsgroup the "connectivity" one?

>
> Secondly - are you using 1.06 ?  The project that you posted works fine for
> me here with 1.06.
>

I am using 1.06 Build 1 and Visual Studio 2008 (Team System).

I just tried the project on another computer and it locked up on that as
well.

Did you recompile the .exe or did you just try running the existing one?
(Just wondering if it might be a problem with VS2008)

It is very strange that the first SELECT works and the second one fails.

Chris Holland

Hi Tim,

I have just looked into this a bit further and it appears to be a
problem with the tables. I migrated them from existing DBISAM 4 tables.

If I delete the first row in the table it no longer freezes, but throws
an exception with a blank exception message.

If I delete row 4 it all works as expected.

I am finding the same problem on a few other tables as well.

I am not sure why the project works at your end!

Chris Holland

Chris,

<< Sorry about that, is the correct ElevateDB newsgroup the "connectivity"
one? >>

Yep.

<< Did you recompile the .exe or did you just try running the existing one?
(Just wondering if it might be a problem with VS2008) >>

I recompiled it with VS2005.

--
Tim Young
Elevate Software
www.elevatesoft.com

Chris,

<< I have just looked into this a bit further and it appears to be a problem
with the tables. I migrated them from existing DBISAM 4 tables.

If I delete the first row in the table it no longer freezes, but throws an
exception with a blank exception message.

If I delete row 4 it all works as expected.

I am finding the same problem on a few other tables as well. >>

The data contents shouldn't matter in the least.

Could you do me a favor and try it with VS2005 ?  This sounds like it may be
an issue with VS2008, especially since it works here for me with VS2005 and
it works in the EDB Manager.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

I suspect it was because the tables that I sent you were a backup and
not a direct copy.

Don't worry about it, I dont need to import the data and I recreated the
tables and all is fine now.

Chris Holland

Tim Young [Elevate Software] wrote:
> Chris,
>
> << I have just looked into this a bit further and it appears to be a problem
> with the tables. I migrated them from existing DBISAM 4 tables.
>
>  If I delete the first row in the table it no longer freezes, but throws an
> exception with a blank exception message.
>
>  If I delete row 4 it all works as expected.
>
>  I am finding the same problem on a few other tables as well. >>
>
> The data contents shouldn't matter in the least.
>
> Could you do me a favor and try it with VS2005 ?  This sounds like it may be
> an issue with VS2008, especially since it works here for me with VS2005 and
> it works in the EDB Manager.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Chris,

<< I suspect it was because the tables that I sent you were a backup and not
a direct copy.

Don't worry about it, I dont need to import the data and I recreated the
tables and all is fine now. >>

So, it appears that the tables were corrupted ?  Have you had any improper
shutdowns or resets ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

The data in the original DBISAM tables is just test data that I use
whilst developing, they quite often just get shutdown in the middle of
developing, so they could well have been damaged before I tried the import.

Chris


>
> So, it appears that the tables were corrupted ?  Have you had any improper
> shutdowns or resets ?
>