Hi Guys,
Using the latest ODBC files with ODBCExpress.  D7Pro +SP1.
Linking and using a single table, no problem.  I can move back & forth
in the table/grid at will.
Setting a master detail with a second table & grid, when ever I move
the
master table I get a "S1106: [Microsoft][ODBC SQL Server Driver]Fetch
type out of range" error.
This is apparently a known ODBC issue.
My question is..There must be a work around to allow Master-Detail
activities without error.  What is it??
Any assistance appreciated.

Regards & TIA,

Ian




--

Ian,

<< master table I get a "S1106: [Microsoft][ODBC SQL Server Driver]Fetch
type out of range" error. This is apparently a known ODBC issue. My question
is..There must be a work around to allow Master-Detail activities without
error.  What is it?? >>

Is this a general ODBC question ?  The reason that I ask is the above error
says "ODBC SQL Server Driver".

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:



Hi Tim,

>
> Is this a general ODBC question ?  The reason that I ask is the above
> error says "ODBC SQL Server Driver".

I guess it is, as it seems to be an acknowledged issue by Microsoft.  I
did in fact paste the wrong error message, the correct one is
"[Microsoft][ODBC Driver Manager]Fetch type out of range".

I figured that someone, anyone, using ODBC with DBISAM has probably
come across this and there is a solution.

Regards,

Ian



--

Ian,

<< I guess it is, as it seems to be an acknowledged issue by Microsoft.  I
did in fact paste the wrong error message, the correct one is
"[Microsoft][ODBC Driver Manager]Fetch type out of range".

I figured that someone, anyone, using ODBC with DBISAM has probably come
across this and there is a solution. >>

Ahh, okay.  In the case of the ODBC Driver Manager errors, there's not much
anyone can do besides MS.  Did you ask the ODBCExpress guys/gals whether
this was something they might be triggering ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

   All sorted.  It seems that some databases via ODBC don't like cursors
moving in one direction or another in 'real time'.  solution is to turn
caching on so there are records available.  All fixed.

Regards,

Ian

Ian,

<< All sorted.  It seems that some databases via ODBC don't like cursors
moving in one direction or another in 'real time'.  solution is to turn
caching on so there are records available.  All fixed. >>

Ahh, so you were using a dynamic cursor result set and not a static one ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

>
> Ahh, so you were using a dynamic cursor result set and not a static
> one ?

Damned if I know.  Still learning about that stuff I just hooked it
together..Database->Tables->DBISAMODBC->ODBCExpress->Datasource->Grids.

Regards,

Ian

Ian,

<< Damned if I know.  Still learning about that stuff I just hooked it
together..Database->Tables->DBISAMODBC-ODBCExpress->Datasource->Grids. >>

In ODBCExpress, it's the hStmt.CursorType property:

Forward-Only = Live result set in DBISAM ODBC (if it can get one)
Static = Canned result set in DBISAM ODBC
Keyset Driven = Canned result set in DBISAM ODBC
Dynamic = Live result set in DBISAM ODBC

--
Tim Young
Elevate Software
www.elevatesoft.com