The back end is some proprietary database. It's basically an unknown since we know almost nothing about it and have very little documentation on it. The database is for a product called Global Shop. They claim it is some sort of COBOL database?

At any rate the tables we're unfiltered until yesterday when I tried to add a filter on one of our SELECT statements in one of the SQLEXEC()'s. I thought if I put in a simple filter it may reduce the resultant cursor size and hopefully speed things up.

They are testing today...

Thanks again,
Don

>
>We created a connection and are using SQLEXEC() to open cursors of data from tables
>in the proprietary database.
>The problem is that opening these tables takes forever and a day.
>I was sort of hoping maybe using SQLPREPARE() might be the answer to my speed issues.
>
>
>Who is backend or ODBC origin data type ?
>
>I think SQLPREPARE() not change the situation, but Try is simple.
>
>You can use MS Query for test the speed,
>and see if the problem is into ODBC Server side.
>
>You read
>a) unfiltered tables
>b) filtered tables
>c) joined tables
>
>?
>
>With b)c) you can have a lack of indices.