It sounds like you could do with getting some ODBC tracing as SQLAllocStmt=-2
means SQL_INVALID_HANDLE (i.e. the connection handle passed to SQLAllocStmt was
invalid).
Assuming this is Windows go into the ODBC administrator and turn tracing on.
What is in this trace file after a run of your Perl?
Martin
On 13-Mar-2003 Bryan Yeung wrote:
> First of all, thank you for all of your help so far. Particularly, for
> explaining where all of those _method calls go.
>
> The bad news is that I did try it and posted a problem I was having to
> the list a little while ago. Unfortunately, no one responded. Upon
> calling tables I get the following error:
>
> DBD::ODBC::db tables failed: (DBD: st_tables/SQLAllocStmt err=-2)
>
> This error, as well as some system info, can be seen in my original
> message ("tables error and make problems").
>
> Bryan
>
> P.S.--I have resolved the make issue.
>
> Jeff Urlwin wrote:
>> Bryan,
>>
>> table_info in DBI maps to the driver's table_info call, which in turn calls
>> SQLTables for you via the _tables() call.
>> column_info does the same...
>>
>> _columns and _tables are implemented in ODBC.xs.
>>
>> The best thing to do is just try it.
>>
>> Jeff
>>
>>
--
Martin J. Evans
Easysoft Ltd, UK
Development
