Alaska Software Inc. - Keywords conflict work around
Username: Password:
AuthorTopic: Keywords conflict work around
Bruce AndersonKeywords conflict work around
on Mon, 09 Nov 2009 10:46:00 -0600
Some operations you might want to do using ActiveX will conflict with 
Alaska's reserved keywords.  If the problem involves a "method" of the 
ActiveX object, the function CallMethod() steps past the conflict, but, if 
the conflict involves a "property" of the object, it is more involved.

The code line to hide a row or column in an Excel spreadsheet will cause a 
compiler failure because the row or column property named "hidden" which you 
set to TRUE is also a reserved keyword.  You can execute this command using 
a codeblock.

       hide row 1
      cBlock := '{|x| x:rows(1):hidden := "TRUE" }'
      bBlock := &(cBlock)
      eval( bBlock, oSheet )
Wolfgang Ciriack Re: Keywords conflict work around
on Mon, 09 Nov 2009 19:28:21 +0100
Bruce Anderson schrieb:
> Some operations you might want to do using ActiveX will conflict with 
> Alaska's reserved keywords.  If the problem involves a "method" of the 
> ActiveX object, the function CallMethod() steps past the conflict, but, 
> if the conflict involves a "property" of the object, it is more involved.
> 
> The code line to hide a row or column in an Excel spreadsheet will cause 
> a compiler failure because the row or column property named "hidden" 
> which you set to TRUE is also a reserved keyword.  You can execute this 
> command using a codeblock.
> 
>       hide row 1
>      cBlock := '{|x| x:rows(1):hidden := "TRUE" }'
>      bBlock := &(cBlock)
>      eval( bBlock, oSheet )
> 

Then you can try x:rows(1):SetProperty("hidden","TRUE")
Regards Wolfgang
Bruce AndersonRe: Keywords conflict work around
on Tue, 10 Nov 2009 07:26:02 -0600
Well, yes, but only if you are really smart!  Thank you for pointing this 
out.  I must have had a case of the dumbs.