From: Bruce D. I. <bru...@ak...> - 2003-02-18 14:41:27
|
Carlos Guzm=E1n =C1lvarez wrote: > [snip] > Ok, thanks for the answer :), if i have time i will make a test using=20 > the Microsoft OdbcTest application you are making this sequence, i=20 > will see with sequence uses Visual Foxpro too, because with it the=20 > ODbc_Jdbc driver works fine : > > SqlPrepare > SqlExecute > SqlNumResultcols > > or > > SqlExecDirect > SqlNumResultCols=20 The function call sequence may be part of the problem. The tool I am having trouble with is called SAS. It is from SAS=20 Institute and is used for data manipulation and statistical analysis.=20 Capturing it's activities in the respective functional versions of the=20 OdbcJdbc driver with OdbcTest I see the following sequence of calls in=20 the trace: FOR INSERT: SqlPrepare SqlExecute FOR SELECT: SqlPrepare SqlNumResultCols SqlDescribeCol SqlColAttributes SqlBindCol SqlExecute SqlFetch Apparently SAS and FoxPro call the SqlNumResultsCol at a different point=20 in the sequence. Bruce Inglish bru...@ak... |