|
ISTech Support Forum
http://www.istechforum.com/YaBB.pl Evo-ERP and DBA Classic >> Problem Reports - Repeatable >> AR-A or AR-Q Print Transactions Grid Issue http://www.istechforum.com/YaBB.pl?num=1256759373 Message started by gtladmin on 10/28/09 at 12:49:33 |
|
Title: AR-A or AR-Q Print Transactions Grid Issue Post by gtladmin on 10/28/09 at 12:49:33 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 |
|
Title: Re: AR-A or AR-Q Print Transactions Grid Issue Post by cathyh on 10/28/09 at 13:57:47 I got this result in AR-Q but my AR-A works fine. in my test that has sept sp3 loaded. |
|
Title: Re: AR-A or AR-Q Print Transactions Grid Issue Post by NovaZyg on 10/28/09 at 14:19:16 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 |
|
Title: Re: AR-A or AR-Q Print Transactions Grid Issue Post by cathyh on 10/29/09 at 09:16:56 I confirm that it works fine if you don't actually print the grid, but just do a print preview, as Val stated in the post on AP-A. That is why I did not have a problem yesterday with AR-A, I did not actually try to print, just brought up a preview and exited without sending the document to the printer. |
|
Title: Re: AR-A or AR-Q Print Transactions Grid Issue Post by Lynn_Pantic on 11/04/09 at 17:03:15 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. |
|
Title: Re: AR-A or AR-Q Print Transactions Grid Issue Post by gtladmin on 11/06/09 at 11:59:46 Well, we are definitely seeing issues with this update. It is much slower in the lookups in our case. Before the patch, when you did a SO lookup in IN-A, the SOLINES window came up after a second or so, and then it took maybe 15-17 seconds to load the data. Now, a small window title bar with no title on it appears in the lower left corner of the Evo Desktop. After 45 or more seconds, that titlebar changes to all whilte (like a white rectangle), then the SOLINES Grid comes up and then it populates. I am also getting reports of fatal errors: Fatal Err: file: WBLOOKUP.SRC LINE 4591 There is a fatal problem with the following expressing. The problem may have to do with the parentheses: (BKAR.INVL.PQTY <> VAL("0" ) ).O. (bkar.invl.ubo ,. val("0" ) ) Also, with PO, our purchasing person reports: Quote:
So....hmmm.....I'll keep reporting. Val |
|
Title: Re: AR-A or AR-Q Print Transactions Grid Issue Post by gtladmin on 11/06/09 at 12:04:52 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 |
|
Title: Re: AR-A or AR-Q Print Transactions Grid Issue Post by RPCAdmin on 11/06/09 at 12:13:22 Yikes indeed, deleting PO's is not good.....However..... Michelle says "I was in a PO I just entered......" does this mean she entered it, verified it was in the PO listing and then edited it.....(and then it was deleted)...or was she in the process of entering it "I just entered and clicked on "notes" to enter one and got the error:....." - which means she may not have "saved" it when the error occured? |
|
Title: Re: AR-A or AR-Q Print Transactions Grid Issue Post by gtladmin on 11/09/09 at 08:07:34 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 |
|
Title: Re: AR-A or AR-Q Print Transactions Grid Issue Post by gtladmin on 11/09/09 at 12:54:01 Another item on the update installed last week: I have also been told by users they occassionally get the error Warn Err - file:WBKLOOKUP.SRC Line: 518 A record was not found in FILELOC for file - .B04 -2. The must be a records for each file opened. I think they get this as a snowball from a previous error they are trying to get out of, just wanted to report it because I've seen it a few times already. They see it when in IN-A and doing grid lookups, typically for sales orders. Val |
|
Title: Re: AR-A or AR-Q Print Transactions Grid Issue Post by gtladmin on 11/11/09 at 17:06:04 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 |
|
Title: Re: AR-A or AR-Q Print Transactions Grid Issue Post by NovaZyg on 11/12/09 at 01:02:46 I don't want to sound like a broken record... but Archive.... that will speed up your grid queries.. And with SP4 you no longer have to get out of Evo if/when you get that error. just exit that program. The lookups prior to SP4 were a DLL and had a memory leak. Once you got the parentheses error you had to exit. Now each program calls the lookups as a sub program so unloading the calling program unloads memory. Just a question but how much memory (RAM) does the PC(s) getting this error have? Line 4593 is a compile in memory call and if you look at the parentheses they do match, so it is not parentheses but memory that is the real issue here. |
|
Title: Re: AR-A or AR-Q Print Transactions Grid Issue Post by cathyh on 11/12/09 at 08:48:50 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. |
|
Title: Re: AR-A or AR-Q Print Transactions Grid Issue Post by gtladmin on 11/16/09 at 07:54:11 Allen to answer your question, all my systems have 2GB of RAM. Val |
|
ISTech Support Forum » Powered by YaBB 2.1! YaBB © 2000-2005. All Rights Reserved. |