Reason Code Analysis Report and PartTran Table

Yahoo Archive
1
The reason codes are stored in the reason file with company, reasoncode, and
reasontype as the unique indexes.

The parttran file uses trantype as its reason code.

A sample Progress query (editor) to view all tran types in your parttran

Find first company no-lock no-error.
For each parttran no-lock where parttran.company = company.company
Break by parttran.trantype.
If first-of(parttran.trantype) then
Display parttran.trantype.

End.



CorVu will be faster than ODBC because it uses a direct connect to your
database.

Contact Amazon for a Progress book called - OpenEdge Development - Progress
ABL Handbook by John Sadd

It will give a lot of good examples in creating Progress views

Carl Peterson

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
mintokmint
Sent: Saturday, November 22, 2008 5:53 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Reason Code Analysis Report and PartTran Table

Which table and field stores the Reason code when user input it doing
Part Transcations.
My Vantage is 800.
Many thanks
--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"rwhalebelly" <richard.whalebelly@...>
wrote:
>
> I am trying to do a reason code analysis report which involves
linking
> the PartTran table with the Reason table. However it is incredibly
> slow. Even if I just use the PartTran table on it's own and filter by
> the part number it is slow. I am using an ODBC connection with read
> uncommitted. I seem to have always had this problem with the PartTran
> table. We have Corvu, would it be better to use this. We are on
> Vantage 6.1. Just interested how other people get on.
>
> Thanks for your help in advance
>
> Richard Whalebelly
> Shelbourne Reynolds Eng Ltd
>



[Non-text portions of this message have been removed]
2
I am trying to do a reason code analysis report which involves linking
the PartTran table with the Reason table. However it is incredibly
slow. Even if I just use the PartTran table on it's own and filter by
the part number it is slow. I am using an ODBC connection with read
uncommitted. I seem to have always had this problem with the PartTran
table. We have Corvu, would it be better to use this. We are on
Vantage 6.1. Just interested how other people get on.

Thanks for your help in advance

Richard Whalebelly
Shelbourne Reynolds Eng Ltd
3
Hi,

I would use corvu, it would be quicker and you could add the report
to the corvu schedule.



--- In vantage@yahoogroups.com, "rwhalebelly"
<richard.whalebelly@...> wrote:
>
> I am trying to do a reason code analysis report which involves
linking
> the PartTran table with the Reason table. However it is incredibly
> slow. Even if I just use the PartTran table on it's own and filter
by
> the part number it is slow. I am using an ODBC connection with
read
> uncommitted. I seem to have always had this problem with the
PartTran
> table. We have Corvu, would it be better to use this. We are on
> Vantage 6.1. Just interested how other people get on.
>
> Thanks for your help in advance
>
> Richard Whalebelly
> Shelbourne Reynolds Eng Ltd
>
4
Which table and field stores the Reason code when user input it doing
Part Transcations.
My Vantage is 800.
Many thanks
--- In vantage@yahoogroups.com, "rwhalebelly" <richard.whalebelly@...>
wrote:
>
> I am trying to do a reason code analysis report which involves
linking
> the PartTran table with the Reason table. However it is incredibly
> slow. Even if I just use the PartTran table on it's own and filter by
> the part number it is slow. I am using an ODBC connection with read
> uncommitted. I seem to have always had this problem with the PartTran
> table. We have Corvu, would it be better to use this. We are on
> Vantage 6.1. Just interested how other people get on.
>
> Thanks for your help in advance
>
> Richard Whalebelly
> Shelbourne Reynolds Eng Ltd
>