ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Manufacturing >> Cannot generate PO for Make From after update
http://www.istechforum.com/YaBB.pl?num=1119624924

Message started by tgoodson on 06/24/05 at 06:55:24

Title: Cannot generate PO for Make From after update
Post by tgoodson on 06/24/05 at 06:55:24

I installed the 6/60/05 update and the patch on the 23rd for EVO. The patch fixed one problem, but now, I cannot generate a PO for any Make From parts. I get a series of errors as listed below:

Fatal Error:

Error during internal field find

then press <ENTER> or OK

The field you are trying to use is unallocated. It may belong to a file that hasn't been opened yet or was an array that was removed from memory.

then click OK

The field must be of a type F or P

then click OK

You have tried to access a file that has not been previously opened, or the file number (FNUM) value passed was 0.

Has anyone had this? I need to get this fixed ASAP. HELP!

Title: Re: Cannot generate PO for Make From after update
Post by JNAPIER on 06/24/05 at 07:38:56

Same here!

Title: Re: Cannot generate PO for Make From after update
Post by Lynn Pantic on 06/24/05 at 16:11:19

It is the Evo PO-A, will have a patch by Monday - meanwhile, UT-A, BKPOA.RUN will work.

Title: Re: Cannot generate PO for Make From after update
Post by Lynn Pantic on 06/26/05 at 15:30:57

www.istechsupport.com/dl/620patch.zip file now contains this fix. So does the main download file if you haven't downloaded it yet. Same password as the original post.

Title: Re: Cannot generate PO for Make From after update
Post by tgoodson on 06/27/05 at 03:28:18

I got the fix you sent, Lynn. Now, however, I am getting a message that I have not renewed my IST License when I try to run PO-A. It says I am not entitled to run the newer version. I have a lifetime license, and all other programs seem to run. What now?

Title: Re: Cannot generate PO for Make From after update
Post by tgoodson on 06/27/05 at 05:04:57

I tried to run the PO-A with DBA and it worked fine. I decided to try and download the entire update again and reload it. This seems to have fixed the problem. I hope this may help someone else.

Tommy