Postgres Pro
Downloads
Home   >   mailing lists

Thread: Column Name Length problem?

Column Name Length problem?

From
"Corey W. Gibbs"
Date:
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.
After working on the app for awhile, I had to re-write the database layout based on user requests.  I made some field names longer and others shorter, and generally "neatened things up".  Why does "neatening things up" always break it? :). 
Of course, I didn't document the old layout, so I can't compare where things went wrong.  (Mental note, save printouts of the database layout)
On Friday, "select * from schedule" in the recordset.open statement would cause a "division by zero" error.  In debugging it, I got up to "select id,quote_number,price_required,bid_date,bid_time,project_name from schedule" before I had to leave for the day.  On Monday morning I'm going to start debugging the app from that point, but I was wondering if anyone could see anything that I would need to watch out for in the layout below.  Or that would cause select * to bomb out.
thanks in advance
corey
                    Table schedule in database est_track
     _________________________________________________________________
 
   Field name             Type      Array? Allow nulls?
   id - a serial field    int4      No     No
   quote_number           int4      No     Yes
   price_required         timestamp No     Yes
   bid_date               timestamp No     Yes
   bid_time               timestamp No     Yes
   project_name           text      No     Yes
   location               text      No     Yes
   state                  text      No     Yes
   estimator              text      No     Yes
   job_number             int4      No     Yes
   hund_percent_sell      float8    No     Yes
   percent_sell           float8    No     Yes
   bid_amount             float8    No     Yes
   low_bid_amount         float8    No     Yes
   low_bid_percent        float8    No     Yes
   low_bid_bidder         text      No     Yes
   addl_bid               text      No     Yes
   addl_bid_amount        float8    No     Yes
   spread                 float8    No     Yes
   addl_bidder2           text      No     Yes
   addl_bidder2_amount    float8    No     Yes
   addl_bidder3           text      No     Yes
   addl_bidder3_amount    float8    No     Yes
   addl_bidder4           text      No     Yes
   addl_bidder4_amouint   float8    No     Yes
   spread_percent         float8    No     Yes
   low_bid_notes          text      No     Yes
   low_bid_spread         float8    No     Yes
   low_bid_spread_percent float8    No     Yes
   addl_bidder2_notes     text      No     Yes
   addl_bidder3_notes     text      No     Yes
   addl_bid_notes         text      No     Yes
   rebid                  bool      No     Yes
   rebid_info             text      No     Yes
   sales_person           text      No     Yes
   date_complete          timestamp No     Yes
   no_tabs_avail          bool      No     Yes
   only_bidder            bool      No     Yes
   negotiated             bool      No     Yes
   no_tabs                bool      No     Yes
   dealer_bid             bool      No     Yes
   accept_date            timestamp No     Yes
   date_modified          timestamp No     Yes
   plan_deposit           bool      No     Yes
   plan_return_date       timestamp No     Yes
 

Re: Column Name Length problem?

From
Hiroshi Inoue
Date:
> "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 ?

regards,
Hiroshi Inoue

Re: Column Name Length problem?

From
Corey W.Gibbs
Date:
Good Morning Hiroshi,
That's the weird part, it links up in Access via a linked table ok.
In the VB program i'm using ADODB as shown in the HOWTO on the odbc site.  It used to work :).  I'll turn on the sql
logand see what it's telling me. 
corey

>
> From: Hiroshi Inoue <Inoue@tpf.co.jp>
> Date: 2002/03/04 Mon PM 05:20:42 PST
> To: "Corey W. Gibbs" <cascadia@nventure.com>
> CC: pgsql-odbc@postgresql.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 ?
>
> regards,
> Hiroshi Inoue
>

Re: Column Name Length problem?

From
Corey W.Gibbs
Date:
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
checkedthe 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. 
thank you
corey

>
> From: Hiroshi Inoue <Inoue@tpf.co.jp>
> Date: 2002/03/04 Mon PM 05:20:42 PST
> To: "Corey W. Gibbs" <cascadia@nventure.com>
> CC: pgsql-odbc@postgresql.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 ?
>
> regards,
> Hiroshi Inoue
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>