ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Items >> Open PO report printing due date out of order.
http://www.istechforum.com/YaBB.pl?num=1147195872

Message started by Brian Snyder on 05/09/06 at 09:31:12

Title: Open PO report printing due date out of order.
Post by Brian Snyder on 05/09/06 at 09:31:12

In PO-I-A, we made a modified form called "Vendor Past Due Report" that shows all the past due PO's for a given vendor. It shows the PO#, Item#, Order Qty, Qty Due, and Original Due dates. We also have a blank box for them to fill in the new Promised Ship Date. It works well, but I have noticed when we have multiple items with multiple due dates on a PO, it doesn't print them in order that they are due. For example, we have a PO that has the same part number as four different line items, each with a shipping date one month apart. However, the report lists the due dates as:

05/30/06
06/30/06
03/30/06
04/30/06

Is there some way to get them to print in the correct order that they are due?

Title: Re: Open PO report printing due date out of order.
Post by ginawendelin on 05/25/06 at 08:09:14

We have an issue with this as well. We contacted Lynn quite a while ago about this and she told us to go to the ISTech FAQ's and we found the following.

How can I change the order of the records on a lookup screen such as the Shipments button in AR-A?

Installing a DBA update typically rebuilds a number of files which have changed as a result of adding fields or changing indexes. The result of this is that many screens that appeared to be in a logical order prior to the update are now random. This is because many of the seemingly ordered displays are really in order simply because of the physical location of the records in the file. Invoices are posted and therefore appended to the BKARHINV file more or less in chronological order so the shipments lookup in AR-A appears to be in date/invoice number order. After updating, the data is random so that is no longer the case.

This can be corrected using the Pervasive Rebuild utility and forcing the rebuild to use a specific index (such as invoice number). This rearranges the file in the order specified so when a different index (such as customer code in the AR-A shipments lookup) is used to open the file, the data within that specified index is subsorted by the index used in the Pervasive Rebuild.

Start - Programs - Pervasive - Pervasive SQL 2000 - Utilities - Rebuild.
Click Options - Settings and enter the desired Key Number (you can determine the number of the one you want by opening the file in Maintain Database and using the number specified there under Indexes for Selected File). Click OK, then Options - Select Files - Add and choose the file to reindex. Click OK, Then Run and start rebuild. Of course you should always make sure you have a backup copy of the file and that all users are out of DBA when rebuilding files.

We couldnt get it to work for us, but maybe we did something wrong. Its worth a try, hope it works for you.