Dennis, Karen, Javier
All our EEPs have Comment headers like you suggested, plus descriptive comments 
throughout long EEPs which helps in tracking.  Checked slave table settings. 
Looked at all the EEP boxes, both yellow and clear. Made some print screens of 
the EEP errors. Last shot has 6 lines of 3 ASCII characters each. Changed the 
screen to an updated older version and the problem went away which confirmed 
something was there.  Only time this problem showed was in this particular 
screen.

Now to spend some serious time with SET CHECKPROP ON. 

Tom Frederick
President/CEO
Elm City Center
1314 W Walnut
Jacksonville, IL 62650
O-217-245-9504
F-217-245-2350
[email protected]


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Javier Valencia
Sent: Thursday, February 12, 2015 1:08 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: Hidden EEP

When you TRACE an application, exit TRACE right after an error, make changes 
and re-start TRACE, it will bring out the last error message detected. I 
normally ignore that.
Looks like you might have an unwanted EEP that has a couple of characters 
entered there by mistake.
EEPs that usually "hide" are usually found under Tables>Add or remove table.
Click on the  "Table Settings" button and verify that  the 6 Entry/Exit 
procedures are empty or have valid code; the check box will show yellow when 
there is code and will be blank when there is no code. Click on the every slave 
table and then click the "Settings..." button and do the same thing.

Javier,

Javier Valencia, PE
O: 913-829-0888
H: 913-397-9605
C: 913-915-3137


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Tom Frederick
Sent: Thursday, February 12, 2015 9:20 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Hidden EEP

We must be running a streak. I have had an EEP error message after creating PDF 
files for several weeks. Using TRACE and ECHO I know when the error happens, 
but the ECHOed text after the message varied from gibberish to pieces of recent 
commands. None of the editable EEPs show anything odd.
Today, using TRACE, a custom EEP popped up consisting exclusively of a small 
'I' and a backward cap 'N' in a very small font. It came up consistently.
The Custom EEP ID varied from 81029224 or 81914976. There is still nothing 
viewable in any identifiable custom EEPs that had these characters to ID the 
actual source. I replaced the screen with an updated 3 year old version and now 
it seems to work just fine. Is there some way to use those EEP IDs to find 
where stuff like this is coming from so it can be erased?  Using v95 with 1/09 
update.

Tom Frederick
President/CEO
Elm City Center
1314 W Walnut
Jacksonville, IL 62650
O-217-245-9504
F-217-245-2350
[email protected]<mailto:[email protected]>


Reply via email to