We just updated to 6/13/05 update this morning and found that everytime a transaction is edited in GL-P, EVO duplicates that transaction.
 
For example, I edited the description of an inventory adjustment transaction IN_C in the "OTHER" batch, from "adjustment to stock" to "withdrawn by engineering" to the inventory account 1220.  After I selected "UPDATE" after editing the desription of this transaction, two duplicate records were created, a debit to 1220  and a credit to 1220 that still read "adustment to stock", in addition to the record I edited that reads "withdrawn by engineering."
 
Since I edited four transactions, EVO created 8 additional records. Everytime a transaction is edited, it created a debit and credit record for the same account in the "OTHER" batch.
 
I used F4 to delete these system created duplicate transactions - but would appreciate a "FIX" as soon as possible.
 
PLEASE ADVISE as this is a process I do daily.
 

Since EVO codes all IN-C inventory adjustments to COST OF GOODS SOLD gl account and tags them all with the descripton "adjustment to stock", we have a need to change the gl account number and transaction descriptions when IN_C adjustments are not related to cost of goods sold.  
 
I.E. material withdrawn by engineering is charged to GL for Engineering expense.  Scrapped and not found inventory adjustments are charged to inventory shrinkage GL, not cost of goods sold.  We try to keep the Cost of Goods Sold GL to only reflect the inventory costs related to the inventory items that ship via sales invoices.

GL-P also duplicates records when the effective date is changed!
 
When backing out work order issued material from a prior accounting period, we use AM-A to reset the calendar date to the date of the transaction which needs to be backed out.  Then EVO will allow the work order issue to be backed.  Then I go to GL-P and EDIT  the transaction date from a previous accounting period to the current accounting period and reset AM-A to the current accounting period.
 
With the 6/13 upate, GL-P shows the transaction for the current accounting period, June, but again has duplicated  transaction records to show the prior period (APRIL) date as well as the current period date.
 
I.E. April 11 - credit 1230 WIP  $100
     April 11 - debit 1230 WIP $100
     April 11  -debit 1220 raw material $100
     April 11 - credit 1220 raw material $100
     June 22 - credit 1230 WIP $100  
     June 22 - debit  1220 raw material $100
 
I now have 6 transactions, instead of just 2.

We used to be able to go into GL-P to fix things that got thrown into the 9999-0 account,  It was a simple fix, where you just had to correct the account number.
 
We currently try to fix it, but it won't keep the fix, it still throws the errors into 9999-0 and won't update.  This is only since the last update.
 
Any answers as to how to get this fixed.  I can't post in the GJ, because it's showing a clearing error in my WO's, but we can't fix them in EVO-ERP or regular classic DBA.
 

Is anyone else have this problem with the 9/27/07 update.
(see 6/13/2005) update
 
 I try to modify thru GL-P.  
It appears it is working, but nothing happens and the wrong Xactions are duplicated.
 
I have to go to maintain database to fix thru GLTemp
 

If an invoice gets a wrong date (usually because someone dated the Packing slip) wrong, then I go to GL-P and change the dates on both sides of the Xactions.
 
But now (since the update)  it appears to change the date, but when I go into GL-O it has not, and has actually created a duplicate Xaction with the wrong date.
 
This is almost exactly what happened with the 2005 update, but it did create a new Xaction, but kept the old Xaction.
 
I am wondering if this could be part of Lynn Kissingers GL-O problem?

You know... PervasiveSQL even supports triggers.

that may be true Lynn,  But I like to use it for other stuff too.  
 
* *  A N D * *   if  Every entry is duplicated  (not justing changing invoice dates)  ...
then what purpose does GL-P serve?  and why did you fix it in the past?
 
So what is GL-P for? ?  ?    and can anyone use it right now, and actually get a modified entry.....can anyone use it right now and not get duplicated entries?
 
I could before this last update.