Hi Dan,
I just have a file that I run at the R> prompt to codelock. I have 3
files for every codelocked application. The extensions are APP,
APX, CDL. Below is a sample CDL file.
--requries error variable "gverrvar"
set v v$t$messages = (cval('Messages'))
set messages off
erase START.APX
if gverrvar <> 0 then
pause 2 using 'Cannot delete START.APX. Must be in use.'
else
codelock 5 START.APP START.APX
pause for 2 using 'Codelock successful!'
endif
set messages .v$t$messages
clear var v$t$%
return
Feel free to use it as is or alter it to suit your needs. That goes
for anybody reading this.
Best regards.
Mike Young
On Sun, 21 Apr 2002 12:35:52 -0400, Dan wrote:
>Hi All,
> I am thinking of asking for an enhancement, but wondered If anyone else
>would like this.
>When codelocking an app file, after it is done, you are still presented the
>codelock menu. This would be good if you were hoping to continue multiple
>files, but this is never the case for me. I would prefer to have that
>menu close after codelocking. Does anyone do multiple files on a regular
>basis?
>
>Dan
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
