AR-A Select customer record, click on the transactions button, grid of transactions comes up, click on the print grid button, print window comes up, preview and then print the report, close the report, use F2 to select another customer, get access violation error Access Violation at address 004BE7CA in module  'evoerp.exe'.  Read of address 00000180.  Have to CTRL-ALT-DEL out.
 
Happens in either AR-A or AR-Q.
 
Val

Seems the View programs have issues with trying to do things in the grids twice. it works the first time but on second attempts it fails. I am looking into it. WO-Q, AP-U, AR-Q

We have just uploaded a file to   www.istechsupport.com/dl/evolookups.zip  that includes a recompile of all the new GUI programs that use the grids, using a different approach to loading the grids into memory to eliminate the Internal Stack Errors, Too Many Pops, Access Violations  and other stability issues.  So far so good but we are just testing now.  If you do load this and run into any issues, please email me directly and we will get it addressed.
 
September 2009 update with SP3 is required to install this file.  
 

A followup to the quot on POs from Michelle I just posted....
Quote:

 
Yikes! That PO is definitely not in the PO listing any longer.....
 
Val

Mike, in answer to your question, Michelle said she had definitely saved it because she had the PO number (605545).  If you now look  
at the PO listing, it skips that number.  She says she entered it, saved it, went back in to edit it, and boink! It got deleted.
 
Just following up on this beta patch - we still continue to have many issues with SO lookups in IN-A, keep getting the fatal error for line 4591 (already posted).  They can mostly clear out the errors gracefully and they get out of Evo and go back in and 99% of the time they are able to do what they were trying to do.  We have also gotten the same line 4591 error when customer service is entering a sales order and then opens IN-A to do a lookup.
 
We get random errors looking up shipments in IN-A that go something like this:
 
Error Reading Form
Error reading sbFileInfo.Left:  Out of system resources.  Ignore the error and continue?  NOTE:  Ignoring the error may cause components to e deleted or property values to be lost.  
 
Ignore   Cancel  Ignore All
 
They click ignore and are able to continue with the lookup, but then end up getting out of Evo to make sure the error does not cause problems.
 
At this point, I am getting ready to roll back to my old files since people are getting a little tired of getting out of Evo multiple times during the day.
They get out every time they get an error to eliminate the possibility of a snowball effect and locking up Evo.  And Walter is filling my inbox with messages about this update.  
 
Val
 

After applying the last set of updates (yesterday?), we are still seeing this random error when users are in IN-A using the SO lookup (shopping cart icon):
 
FATAL ERR:  fILE:  WBKLOOKUP.SRC Line:  4593
There is a fatal problem with the following expression.  The problem may have to do with parentheses:  ( BKAR.INVL.PQTY <>VAL ("0" ) ). O. (BKAR.INVL.UBO <> val("0" ) ).
OK
 
Users get out of Evo and go back in and it seems to be fine.  
 
Lookups are still taking 45 or more seconds to bring up that grid.
 
Val

I had the same problem with the disappearing PO after trying to edit notes(with same error messages) but after loading SP4( on my stand alone test) the error does not happen any more.