V6.1 ProjectAnalysis ODBC

Charles,

Excel for raw data will eventually develop a Crystal report... I get the
same error with either.
Progress 91D db
Merant 3.60 32bit Progress SQL92 v9.1D is the ODBC driver

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Charles Paluska - HPN
Sent: Friday, December 01, 2006 2:08 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] v6.1 ProjectAnalysis ODBC



Yes Winter is here - woke up to the sounds of ice cubes hitting my roof
all night long.

What application are you using when linking with ODBC ? Excel, Access,
other?
Is your db Progress or MSSql ?

Charles

----- Original Message -----
From: Lee Ingalls
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Sent: Friday, December 01, 2006 1:48 PM
Subject: [Vantage] v6.1 ProjectAnalysis ODBC

Winter has finally hit the midwest we're in the 60's one day then 6" of
snow the next. So while my truck is being buried I thought I'd toss this
beauty out there ;)

Wondering if anyone has encountered the following:

"Column in table PUB.ProjectAnalysis has value exceeding it's max length
or precision"

when connecting to the Project Analysis table?

Using support page 2137MPS I've opened the ProjectAnalysis table with
the data dictionary and attempted to increase the SQL Properties field
width on some of the larger fields to no avail.

Support doc indicates field widths can be upto 31995 but I don't want to
expand every field. The error gives no indication as to which field is
causing ODBC to error. Tech support said it's trial and error... Lame!

Has anyone else connected to v6.1 ProjectAnalysis table with ODBC and
experienced the Max Length or Precision message then successfully
identified offending field??

Thanks in advance, Lee

E. Lee Ingalls III
Director of IT/TS
Commercial Tool Group
Ph 616.785.8100 x121
Fx 616.785.8210
Winter has finally hit the midwest we're in the 60's one day then 6" of
snow the next. So while my truck is being buried I thought I'd toss this
beauty out there ;)

Wondering if anyone has encountered the following:

"Column in table PUB.ProjectAnalysis has value exceeding it's max length
or precision"

when connecting to the Project Analysis table?

Using support page 2137MPS I've opened the ProjectAnalysis table with
the data dictionary and attempted to increase the SQL Properties field
width on some of the larger fields to no avail.

Support doc indicates field widths can be upto 31995 but I don't want to
expand every field. The error gives no indication as to which field is
causing ODBC to error. Tech support said it's trial and error... Lame!

Has anyone else connected to v6.1 ProjectAnalysis table with ODBC and
experienced the Max Length or Precision message then successfully
identified offending field??

Thanks in advance, Lee

E. Lee Ingalls III
Director of IT/TS
Commercial Tool Group
Ph 616.785.8100 x121
Fx 616.785.8210

lee.ingalls@...
Yes Winter is here - woke up to the sounds of ice cubes hitting my roof all night long.

What application are you using when linking with ODBC ? Excel, Access, other?
Is your db Progress or MSSql ?

Charles


----- Original Message -----
From: Lee Ingalls
To: vantage@yahoogroups.com
Sent: Friday, December 01, 2006 1:48 PM
Subject: [Vantage] v6.1 ProjectAnalysis ODBC


Winter has finally hit the midwest we're in the 60's one day then 6" of
snow the next. So while my truck is being buried I thought I'd toss this
beauty out there ;)

Wondering if anyone has encountered the following:

"Column in table PUB.ProjectAnalysis has value exceeding it's max length
or precision"

when connecting to the Project Analysis table?

Using support page 2137MPS I've opened the ProjectAnalysis table with
the data dictionary and attempted to increase the SQL Properties field
width on some of the larger fields to no avail.

Support doc indicates field widths can be upto 31995 but I don't want to
expand every field. The error gives no indication as to which field is
causing ODBC to error. Tech support said it's trial and error... Lame!

Has anyone else connected to v6.1 ProjectAnalysis table with ODBC and
experienced the Max Length or Precision message then successfully
identified offending field??

Thanks in advance, Lee

E. Lee Ingalls III
Director of IT/TS
Commercial Tool Group
Ph 616.785.8100 x121
Fx 616.785.8210

lee.ingalls@...




[Non-text portions of this message have been removed]