DMRCorAct Table

Yahoo Archive
1
Stephen, thank you. This solution worked great, just as you mentioned
below. Again, Thank You!

--- In vantage@yahoogroups.com, "Stephen Edginton" <stephene@...>
wrote:
>
> To clarify the SQL width I mentioned.
>
>
>
> Open Data Administration and connect to your database (test or pilot
> first)
>
> (Note you will need to be in single user mode to modify (i.e.
disconnect
> users V6))
>
> Then choose Tools->Data Dictionary
>
> For example select the Table DMRCorAct
>
> Choose SQL options-> adjust field width (progress 9.1D )
>
>
>
>
>
> The SQL width is what is used when accessing the database via ODBC /
> JDBC. The problems that can occur are that there are more
characters in
> the field than specified in the width.
>
> "ODBC error:[DataDirect-Technologies][ODBC PROGRESS driver]
[PROGRESS]
> Column CauseInv in table PUB.DMRCorAct has value exceeding its max
> length or precision"
>
> The error detailed is that of an ODBC error indicating that SQL
width is
> the issue here.
>
> Note the Width of the CauseInv is set to 16, update this to 2000
and you
> should not get this ODBC error.
>
>
>
> Jill points out particular limitations of Crystal 8.5 this would
result
> in a different error / truncated data.
>
>
>
> Hope this helps
>
>
>
> Stephen Edginton
>
> ________________________________
>
> From: Jill Pleau [mailto:jpleau@...]
> Sent: 25 September 2006 21:56
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: DMRCorAct Table
>
>
>
> I'd be interested in the resolution to this problem. It's been my
> understanding that Crystal 8.5 has limitations in regards to the
huge
> comment fields that are in the newer versions of Vantage -- the fix
> answer that I've gotten from the crystal groups are simply --
upgrade to
> Crystal 10. So I run problem reports in 10.
>
> I didn't understand the comment from Stephen about increasing the
SQL
> width for these fields; this is done with data administration tool??
> Thanks, Jill
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
2
Trying to run a Crystal Report on this table. Two fields are giving me
some fits. CommentText, AuditCmts, and CauseInv are all structured the
same according to Data Dictionary, which are (Fmt:X(1000)) and
(Type:character).
In Crystal Reports 8.5.2.718 The Field Types for these fields are;
CommentText:Memo, AuditCmts:String(16), and CauseInv:String(16). Of
course the CauseInv field is causing me to have a Database Error, since
we already have comments entered in these fields that are more than 16
characters.
The Error:
"ODBC error:[DataDirect-Technologies][ODBC PROGRESS driver][PROGRESS]
Column CauseInv in table PUB.DMRCorAct has value exceeding its max
length or precision"
Anyone else have this problem if they run a reoprt on thid table with
these fields. I already submitted this problem to Epicor, and they are
looking into it. Just wondering what kind of answer I can get from
everyone here. We are running Vantage ver:6.10.535

Thanks In Advance
3
You need to increase the SQL width for these fields; this is done with
data administration tool.



________________________________

From: Ace_Man [mailto:ace_man@...]
Sent: 23 September 2006 18:19
To: vantage@yahoogroups.com
Subject: [Vantage] DMRCorAct Table



Trying to run a Crystal Report on this table. Two fields are giving me
some fits. CommentText, AuditCmts, and CauseInv are all structured the
same according to Data Dictionary, which are (Fmt:X(1000)) and
(Type:character).
In Crystal Reports 8.5.2.718 The Field Types for these fields are;
CommentText:Memo, AuditCmts:String(16), and CauseInv:String(16). Of
course the CauseInv field is causing me to have a Database Error, since
we already have comments entered in these fields that are more than 16
characters.
The Error:
"ODBC error:[DataDirect-Technologies][ODBC PROGRESS driver][PROGRESS]
Column CauseInv in table PUB.DMRCorAct has value exceeding its max
length or precision"
Anyone else have this problem if they run a reoprt on thid table with
these fields. I already submitted this problem to Epicor, and they are
looking into it. Just wondering what kind of answer I can get from
everyone here. We are running Vantage ver:6.10.535






[Non-text portions of this message have been removed]
4
Any instructions on how I would even begin to do this?

--- In vantage@yahoogroups.com, "Stephen Edginton" <stephene@...>
wrote:
>
> You need to increase the SQL width for these fields; this is done
with
> data administration tool.
>
>
>
> ________________________________
>
> From: Ace_Man [mailto:ace_man@...]
> Sent: 23 September 2006 18:19
> To: vantage@yahoogroups.com
> Subject: [Vantage] DMRCorAct Table
>
>
>
> Trying to run a Crystal Report on this table. Two fields are giving
me
> some fits. CommentText, AuditCmts, and CauseInv are all structured
the
> same according to Data Dictionary, which are (Fmt:X(1000)) and
> (Type:character).
> In Crystal Reports 8.5.2.718 The Field Types for these fields are;
> CommentText:Memo, AuditCmts:String(16), and CauseInv:String(16). Of
> course the CauseInv field is causing me to have a Database Error,
since
> we already have comments entered in these fields that are more than
16
> characters.
> The Error:
> "ODBC error:[DataDirect-Technologies][ODBC PROGRESS driver]
[PROGRESS]
> Column CauseInv in table PUB.DMRCorAct has value exceeding its max
> length or precision"
> Anyone else have this problem if they run a reoprt on thid table
with
> these fields. I already submitted this problem to Epicor, and they
are
> looking into it. Just wondering what kind of answer I can get from
> everyone here. We are running Vantage ver:6.10.535
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
5
I'd be interested in the resolution to this problem. It's been my
understanding that Crystal 8.5 has limitations in regards to the huge
comment fields that are in the newer versions of Vantage -- the fix
answer that I've gotten from the crystal groups are simply -- upgrade to
Crystal 10. So I run problem reports in 10.

I didn't understand the comment from Stephen about increasing the SQL
width for these fields; this is done with data administration tool??
Thanks, Jill






[Non-text portions of this message have been removed]
6
To clarify the SQL width I mentioned.



Open Data Administration and connect to your database (test or pilot
first)

(Note you will need to be in single user mode to modify (i.e. disconnect
users V6))

Then choose Tools->Data Dictionary

For example select the Table DMRCorAct

Choose SQL options-> adjust field width (progress 9.1D )





The SQL width is what is used when accessing the database via ODBC /
JDBC. The problems that can occur are that there are more characters in
the field than specified in the width.

"ODBC error:[DataDirect-Technologies][ODBC PROGRESS driver][PROGRESS]
Column CauseInv in table PUB.DMRCorAct has value exceeding its max
length or precision"

The error detailed is that of an ODBC error indicating that SQL width is
the issue here.

Note the Width of the CauseInv is set to 16, update this to 2000 and you
should not get this ODBC error.



Jill points out particular limitations of Crystal 8.5 this would result
in a different error / truncated data.



Hope this helps



Stephen Edginton

________________________________

From: Jill Pleau [mailto:jpleau@...]
Sent: 25 September 2006 21:56
To: vantage@yahoogroups.com
Subject: [Vantage] Re: DMRCorAct Table



I'd be interested in the resolution to this problem. It's been my
understanding that Crystal 8.5 has limitations in regards to the huge
comment fields that are in the newer versions of Vantage -- the fix
answer that I've gotten from the crystal groups are simply -- upgrade to
Crystal 10. So I run problem reports in 10.

I didn't understand the comment from Stephen about increasing the SQL
width for these fields; this is done with data administration tool??
Thanks, Jill

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





[Non-text portions of this message have been removed]
7
Thank you, I'll give that a try. Epicor got back with me and
duplicated what I came across with and they said that they have to
have their Development team look at it.

--- In vantage@yahoogroups.com, "Stephen Edginton" <stephene@...>
wrote:
>
> To clarify the SQL width I mentioned.
>
>
>
> Open Data Administration and connect to your database (test or pilot
> first)
>
> (Note you will need to be in single user mode to modify (i.e.
disconnect
> users V6))
>
> Then choose Tools->Data Dictionary
>
> For example select the Table DMRCorAct
>
> Choose SQL options-> adjust field width (progress 9.1D )
>
>
>
>
>
> The SQL width is what is used when accessing the database via ODBC /
> JDBC. The problems that can occur are that there are more
characters in
> the field than specified in the width.
>
> "ODBC error:[DataDirect-Technologies][ODBC PROGRESS driver]
[PROGRESS]
> Column CauseInv in table PUB.DMRCorAct has value exceeding its max
> length or precision"
>
> The error detailed is that of an ODBC error indicating that SQL
width is
> the issue here.
>
> Note the Width of the CauseInv is set to 16, update this to 2000
and you
> should not get this ODBC error.
>
>
>
> Jill points out particular limitations of Crystal 8.5 this would
result
> in a different error / truncated data.
>
>
>
> Hope this helps
>
>
>
> Stephen Edginton
>
> ________________________________
>
> From: Jill Pleau [mailto:jpleau@...]
> Sent: 25 September 2006 21:56
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: DMRCorAct Table
>
>
>
> I'd be interested in the resolution to this problem. It's been my
> understanding that Crystal 8.5 has limitations in regards to the
huge
> comment fields that are in the newer versions of Vantage -- the fix
> answer that I've gotten from the crystal groups are simply --
upgrade to
> Crystal 10. So I run problem reports in 10.
>
> I didn't understand the comment from Stephen about increasing the
SQL
> width for these fields; this is done with data administration tool??
> Thanks, Jill
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
8
You would use the same instructions in 3604MPS to widen a comment field as you would to truncate a memo field.
I just did changed the SQL field width on CommentText, CauseInv and AuditCmts fields in this table so we can report data collected for our ISO certification.

Phyllis Thé
Accounting Manager/Vantage Project Leader

________________________________

From: Phyllis The
Sent: Monday, March 20, 2006 10:45 AM
To: 'vantage@yahoogroups.com'
Subject: Crystal & Epicor Arrays



The array fields are too big for Crystal 8.5 to handle so you need to truncate them before you can parse the data.

Contact Vantage Support and ask for 3604MPS "How to truncate a memo field".

(I don't have it in electronic form anymore or I would have attached it here. )

We have used this for Rep List and Rep Commissions and a couple other memo/array fields.

A few words to the wise:

1. Use the Sysprogress login and password;

2. Do not take the database down but there must be NO users in the table you are modifying.

3. This change must be done separately for your training database as well .

Good luck!



Phyllis



Message: 1

Date: Fri, 17 Mar 2006 15:45:50 -0500

From: "Bruce Butler" <bbutler@...>

Subject: Crystal & Epicor Arrays

Does anyone know how to get a Crystal 8.5 formula to parse out an field

array? Crystal keeps telling me it does not accept "blog" or "memo"

fields in a formula. Specifically, I am looking at the Machine table

and the hours array.

Bruce Butler, IT Manager

Knappe & Koester <http://www.knappe-koester.com/ <http://www.knappe-koester.com/> >

18 Bradco Street

Keene, NH

p. 603-355-1166

f. 603-355-2266

bbutler@...



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