Memory Error Issue - Need some ideas I am fresh out

[flowersoft at compuserve.com]

Top post.
I had a similar problem recently but with a system call,  After the system
call, the customer would get a memory error every time.  I was not getting
it in my system.  I downloaded his data and then I started getting the error
too.  
I put an errorbox right after the system call, trying to find the exact
location where the error took place and then the error would not occur.  So
you could say that the errorbox fixed the problem. :-)  However, I then
replaced the errorbox with a close statement and the error did not occur
anymore.  If I removed the close statement, the error would come back.  It
was not a "Too many open files" error but a memory error from the operating
system. As I said, it did not happen to me until I downloaded his data into
my system.  So it could be anything but I would try a close to see if it
helps.

-----Original Message-----
From: filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com
[mailto:filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com]
On Behalf Of Nancy Palmquist
Sent: Tuesday, December 06, 2011 12:42 PM
To: filePro Mailing List
Subject: Memory Error Issue - Need some ideas I am fresh out

We are installing a big update for FastEMC and so far one customer has 
this issue.

After saving a claim (record) it runs a CALL table to validate the 
data.  Same for everyone.

On this customer it crashes every time it hits the CALL table.

If I have them call a different table first by running another option on 
the claim, then the Validation CALL table works without the memory 
error.  And on each claim after that it continues to work without 
incident for new and updated claim records as long as they do not leave 
rclerk.

This same solution - does not work on a client just the server.

Windows system with 1 gig+ of memory and 256 gig of drive space.  It is 
Windows XP SP3.  Filepro version 5.0.14 running rclerk and rreport.

*Things I have tried*
I put a small call table into the programming before the validation call 
but that did not seem to fix it.
Checked the TOK size variables - all set as they are for my testing and 
my other customers.
Checked EDITS - it is good.
made sure PFCMARK was set correctly.
ReTOKENIZED all tables - since other people have installed these same 
files without issue - I think that is unlikely the cause.
Rebuilt all indexes to make sure any date indexes were functioning 
correctly - that has thrown memory errors in the past.
Made a copy of the entire setup to make sure we were not having an IO 
issue with any files.  Obviously a corrupt file would be copied corrupt 
but it was something.
Copied file does the same behavior.
Installed all current patches to my programming.  -   Might want to 
reinstall the entire thing maybe - might be an idea.

Any suggestions would be greatly appreciated.  I hate to leave them 
crippled but at least they can add some claims and get paid.  Any 
insight into why this worked, might give me something I can try to 
stabilize their system.

I am thinking remove all indexes and rebuild - during the installation 
of the upgrade that was done, but after all this testing might be good 
to do again.  I have my doubts that that is my problem.

HELP
Nancy

-- 
Nancy Palmquist         MOS&  filePro Training Available
Virtual Software Systems    Web Based Training and Consulting
PHONE: (412) 835-9417           Web site:  http://www.vss3.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.celestial.com/pipermail/filepro-list/attachments/20111206/171
ce83d/attachment.html 
_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
Subscribe/Unsubscribe/Subscription Changes
http://mailman.celestial.com/mailman/listinfo/filepro-list