Copy_Row generates error SYS1006 in runtime (OpenInsight Specific)
At 01 DEC 1999 01:13:41AM Michelle wrote:
Copy_row generates error SYS1006 in an OpenInsight version 3.7 runtime environment.
(EQU SYS_RUNTIME_RESTRICT_ERR$ TO "SYS1006" /* module %1% terminated due to Runtime restriction */)
Is this normal (=copy_row is not allowed to be used in a runtime environment), or is there a patch for it somewhere?
At 01 DEC 1999 05:58AM cpates@sprezzatura.com - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
Michelle,
What records are you trying to copy?
Copy_Row AFAIK is not runtime protected itself, but if you were copying dictionary records for instance you may get an error like this as DICT.MFS may protest and set that flag.
Also are you setting the status to 0 ( Call Set_Status( 0 ) ) before calling copy_row just make sure all errors are cleared before you start?
cpates@sprezzatura.com
World Leaders in all things RevSoft
At 01 DEC 1999 01:02PM Don Miller - C3 Inc. wrote:
CopyRow will do data records just fine in RDK. Won't do DICT records unless they are surrounded by %signs% (control records not of type F or S). It is possible to copy %SK% or other user dict control records that don't have an F or S in the TYPE field.
Don Miller
C3 Inc.
At 01 DEC 1999 01:10PM amcauley@sprezzatura.com onmouseover=window.status=why not click here to send me email?;return(true)", [url=http://www.sprezzatura.com" onMouseOver=window.status=Why not click here to visit our web site?';return(true)]Sprezzatura Group[/url] wrote:
Although of course the runtime license does not make provision for that so it is still a breach.
amcauley@sprezzatura.com
World Leaders in all things RevSoft
At 01 DEC 1999 03:14PM Don Miller - C3 Inc. wrote:
Andrew .. I don't think it technically violates the license since you need to be able to manipulate %SK% programably (batch adding data records, for example) or to reset it for whatever reason (for example a check file which uses %SK% to keep check #'s and somebody needs new numbers. Perhaps creating a new dict record would, but even then I'm not sure.
Don M.
At 01 DEC 1999 03:52PM amcauley@sprezzatura.com onmouseover=window.status=why not click here to send me email?;return(true)", [url=http://www.sprezzatura.com" onMouseOver=window.status=Why not click here to visit our web site?';return(true)]Sprezzatura Group[/url] wrote:
Whoops, forgot to mention the 'overly literal interpretation'
amcauley@sprezzatura.com
World Leaders in all things RevSoft
At 02 DEC 1999 11:40AM akaplan@sprezzatura.com - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
Seems like this is the sort of conversation one should be having in the Licensing & Deployment Discussion Area. Maybe the legal eagles at Revelation would like to make a Soloman like ruling.
akaplan@sprezzatura.com
At 03 DEC 1999 09:52AM Kurt Baker (Revelation) wrote:
I see two questions in this thread:
1. The first is the failure of a copy to a Dictionary in a Runtime. This function is not allowed in a runtime and a development ready license is the appropriate license..
2. The second is %SK% - the function of %SK% is to update a sequential counter at runtime - this capability is enabled in a runtime.
Thanks for asking.
Kurt