On 4/21/2014 11:56 AM, Desmond Lloyd wrote:
HELP!
I just bet one of you has experienced this problem and can offer all sorts
of words of wisdom and advice.....
Had a large program file that was generating "program too large" errors
when trying to compile. There is a whole slew of separate procedures and
functions in the original procedure file, so I moved those out to a
separate file. At the beginning of the original program I set procedure
to the new program name and everything seemed to work....
Note that a procedure file was already set at the time, so I made sure
that I issued the additive command at the end of set procedure to.
Worked fine (several months). Last week I started to experience the
original program too large message again so I once again moved some
procedure and functions to the new procedure file.
Began to get errors that file could not be found when executing "valid
functions" after certain reads. Solution was to move those back to the
original program file.
Testing in my development environment showed that the program worked
fined, however after moving it into my "production environment" users are
getting intermittent cannot find file when running the application. It is
like it "forgot" it has this other procedure file open. Have added some
"occasional checks" to make sure that the procedure file is open. Not sure
if is actually executing or not.
I have used procedure files in the past, as I am sure everyone else has,
and never experience this before.
I can go back to the original code and modify to include the "in" clause.
But at a loss how to correct. This entire program needs to be re-written,
That will take time, and in the interim everybody has to use it....
Any thoughts or suggestions?
Regards,
Desmond
Desmond: One thing I used to run into which may or may not be related
is that if you run an executable - let's say myexternalproc - and we
issue a SET PROCEDURE TO myexternalproc ADDITIVE. All is well. Now
let's make a change to myexternalproc and copy it to the production
machine. All is well again because it looks like it copied over the
original myexternalproc. Since myexternalproc was in memory it does not
copy over the running one even though it looked like the copy was
successful.
Like I said, I don't know if that is related to your problem but I offer
it at no extra charge. ;^)
--
Jeff
Jeff Johnson
[email protected]
SanDC, Inc.
623-582-0323
Fax 623-869-0675
http://www.san-dc.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
