Re: Win32::ODBC - connecting to Remedy AR System

You might find it useful to check for errors and write debugging information like:

if ($odbc->Error) {
    $odbc->DumpError;
    exit;
}
[download]

Checking after you call FetchRow might help. Also you might need to increase your buffer size (in bytes): $odbc->SetMaxBufSize(50_000); I've found that ODBC has problems with memo fields in Access and this has helped. It seems to skip rows that are bigger than the maximum buffer size without flagging an error. I've had success cranking this number up to a meg or so (though record retrieval is slow).

Hope this helps...

gav^

Comment on Re: Win32::ODBC - connecting to Remedy AR System Select or Download Code

Replies are listed 'Best First'.
Re: Re: Win32::ODBC - connecting to Remedy AR System by osfameron (Hermit) on Jun 19, 2002 at 14:31 UTC
Hmm, placing a few error-checks as above gets me (after DumpData or FetchRow) `---------- Error Report: ---------- Errors for "16" on connection 1: Connection Number: 1 Error number: 911 Error message: "[Microsoft][ODBC Driver Manager] Driver does not suppo +rt this function" -----------------------------------` [download] This is despite the fact that DumpData does do something (show the column names). I guess that part of the API call that it makes is unsupported by this driver? Cheerio! Osfameron http://osfameron.perlmonk.org/chickenman/	[reply] [d/l]
Re: Re: Re: Win32::ODBC - connecting to Remedy AR System by LostS (Friar) on Jan 23, 2003 at 17:20 UTC
Don't know if you still concerned with this... But I figured it out... Use DBD::ODBC NOT the Win32::ODBC... If you are just doing selects like I am... the DBI module works wonderfully.... ----------------------- Billy S. Slinar Hardtail - Hand of Dane Datal Ephialtes - Guildless RallosZek.Net Admin/WebMaster `perl -e '$cat = "cat"; if ($cat =~ /\143\x61\x74/) { print "Its a cat! +\n"; } else { print "Thats a dog\n"; } print "\n";'` [download]	[reply] [d/l]


go ahead... be a heretic
	PerlMonks