Good Morning Hiroshi,
I think this problem is a VB related issue. Once i split the statement into two select statements, it worked just fine. Access97 had no problem with linking the table, but VB seems to be choking on this long string of data. I checked the log file, and it fetched the record requested, so it's not the ODBC driver. I did the split right after "spread_percent" and just put the additional columns into a second recordset.
> From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
> Date: 2002/03/04 Mon PM 05:20:42 PST
> To: "Corey W. Gibbs" <cascadia(at)nventure(dot)com>
> CC: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Column Name Length problem?
> > "Corey W. Gibbs" wrote:
> > Good Morning Everyone,
> > I had a perfectly good working application written in VB that tied to
> > a PG database on a Red Hat system with the latest ODBC driver.
> What kind of access method are you using ?
> Aren't you using link tables ?
> Hiroshi Inoue
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
pgsql-odbc by date
|Next:||From: Dave Page||Date: 2002-03-04 19:41:01|
|Subject: Re: Basic ODBC/PostgreSQL|
|Previous:||From: Corey W.Gibbs||Date: 2002-03-04 15:06:34|
|Subject: Re: Column Name Length problem?|