Jim,
If the eep or your command code fails or doesn't complete running, rbase
doesn't clear access to it(locks the file OS level)!
I've found this to be true when I've done incorrect coding with while
loops(exit incorrectly) and eeps(running one before the other finishes)!
The only way to clear it is to exit rbase. You can always save your file to
temp directory and exit rbase and reenter rbase and then save the file in
your working directory(using SAVE AS in RCODE).
If you are running an eep (layout/table setting/after save row)
TALLDRUD.EEP.
Eliminate the saverow in helpskip.eep. The HELPSKIP.EEP is not able to
complete because TALLDRUD.EEP takes control!
This is most likely the source of your problem. HELPSKIP.EEP is in
limbo!!!! Which cause RBASE to respond with the error message you get about
Insufficient memory...!???
Reorder the commands in HELPSKIP.EEP if you don't have an entry epp on
vtype.
SKIP TO vtype
NEWROW
Or add TALLDRUD.EEP before the return in your example of HELPSKIP.EEP?
I am not sure I understand the use of TALLDRUD.EEP? Could you explain that
to me?
Are you putting data into a table other than the one you saved the row to?
Have you used Trace to step through you code and the eep's in your form?
If you like, call me at 662.378.4351 to discuss further glad to help!
I'll be here all day except between 12:00CST and 1:00CST,
I've got a client who has Email Problems and I'll have lunch at their place
while I fix his problem.
Best regards,
Oma
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of J. Andrus
Sent: Thursday, June 14, 2001 7:18 AM
To: [EMAIL PROTECTED]
Subject: RE: Push Button Actions - Razzak's Reply
Razzak,
In stepping through your suggestions and in preparation to respond to Oma's
06/13/01 1:00PM message I encountered something unusual which probably is a
factor in my problem.
Using RCODE as my editor I went through each EEP checking with RSTYLE. All
showed no errors and could be saved without a problem except HELPSKIP.EEP.
Since I had not run RSTYLE on that file before it made the caps/lower case
format corrections, and when I tried to save it I got "Cannot create file
C:\rbti\rbwin65\myfiles\contractor\helpskip.eep". The only way I can save
the changes made by RSTYLE to HELPSKIP.EEP is to exit the RBASE session and
start over. It works OK then. It is as though HELPSKIP.EEP is still in use
and can't be modified until it is closed by ending the session.
This is HELPSKIP.EEP which is executed when leaving the last field on the
form before the HELP button which I want to by-pass.
===================================
--HELPSKIP.EEP
--Exit from VMEAID in FTran & FTran2
SAVEROW
NEWROW
SKIP TO vtype
RETURN
===================================
Perhaps significant to the "Insufficient memory..." problem (not
necessarily the "Cannot create...") problem is that I run TALLRUD.EEP after
the row is saved.
================================================================
--TALLDRUD.EEP
--Run after row saved in FORD, FCAT, FPROJ, FTRAN, FTRAN2,& FCONT
--Record changes to tables TOrd, TCat, TProj, TTran, and TCont
RECALC
--Identify table being updated
SET VAR vftbl = (#FORM_TABLENAME)
--Identify that table's Activity Table
SET VAR vftbl = (.vftbl + 'r')
--Update appropriate Activity Table
INSERT INTO .vftbl (lad,lac) VALUES (.vlad,.vlac)
--INSERT INTO tordr (lad, lac) VALUES (.vlad,.vlac)
RETURN
===================================================================
Clearing all variables and checking the form expressions didn't show any
errors.
All EEPs checked by RSTYLE showed no errors.
When running the form I get no other error messages .
The TTran table and its activity table TTranR are both updated correctly
using all three modes of running the form.
As I mentioned in earlier posts, the "Insufficient memory..." problem does
not occur when running the form from OBJ MGR, only from the R> and my
application.
Jim
