Well, I got my answer from support... Not too thrilled either, as it makes life harder doing things this way. I will include what I was told:


Josh,

The changes to the Order History View were made deliberately to correct the following issues:

Bug report-Customer avail rel - 42.569.865

OE History View by Item is significantly slower in 7.7.700. This was due to changes made for Bug #40.748.947 which reads in part:

"The OE Order History View By Item is not sorting correctly. The Normal OE Order History View and Reverse OE Order History View Listbox Lines display out of order."

This was first resolved by changing the Alternate Key Lookup on the OELINHST Table from Item/Location to TRX-ID while using a SQL-WHERE to filter for the correct Item Number prior to each File Start.

While this solution did put the display into Order Number Order, for larger OELINHST Tables, it also had the effect of slowing down the processing and display of records. Now, instead of going into the table based on a specific Item Number, the entire Table had to be read and filtered for the correct Item and/or Customer Combination.

The next solution (Version 47) varied the Alternate Key that was being used on OELINHST, depending on the parms that the user entered.

However, this solution caused problems when moving backward through the table (using the double arrow keys) because of a conflict between the key in use, and what different key elements in the records were being compared to, on their way backward.

The current solution simplifies the code to use one key moving forward and a similar key going backward. Both keys will allow for proper comparisons to be made between key elements in the records and what they are being compared to, both forward and backward.

Bear in mind that the following still holds true:

All 'C' Type Orders (if any) will appear at the beginning of the listbox display
All 'Q' Type Orders (if any) will appear the end of the listbox display

OEINQITM.DLL 77.800.0.48

We also found that a Screen Change needed to be made to: OEITMHSQ. The "Hold Status" Literal was partially invading the double arrows and needed to be moved to the left. Otherwise, the double arrows moving backward would not work.

Josh,

You can create your own search. What exactly would you like to do? Can you write your own SQL?

Software Training, Implementation, Programming and Support for Macola Progression, Macola ES, Synergy, and Crystal Reports. Check out our Macola tools: www.gainfocus.biz/exceladdin.html