18.01.2013 Views

LotusScript for Visual Basic Programmers - IBM Redbooks

LotusScript for Visual Basic Programmers - IBM Redbooks

LotusScript for Visual Basic Programmers - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

would execute but give incorrect results since you would always compare<br />

whatever the contents of rc was to zero.<br />

Const vbAbort = 3<br />

Const vbRetry = 4<br />

Const vbIgnore = 5<br />

Const vbYes = 6<br />

Const vbNo = 7<br />

Summary<br />

It’s probably safe to say that a lot of your <strong>Visual</strong> <strong>Basic</strong> calculation code will<br />

port across to <strong>LotusScript</strong>, but that your interface code will not move as<br />

easily.<br />

<strong>LotusScript</strong> is enough like <strong>Visual</strong> <strong>Basic</strong>’s BASIC language implementation<br />

that you will have few problems porting code from one tool to the other —<br />

if you recognize these differences be<strong>for</strong>e building any code. With a little<br />

care, you will be able to easily create routines that can be called from either<br />

<strong>Visual</strong> <strong>Basic</strong> or <strong>LotusScript</strong> without change.<br />

The problem <strong>for</strong> the <strong>Visual</strong> <strong>Basic</strong> developer writing code to share with<br />

<strong>LotusScript</strong> will not be what cannot be moved into <strong>LotusScript</strong>. Rather, it<br />

will be in deciding not to use some of the appealing <strong>LotusScript</strong> extensions<br />

that are now available — like class inheritance, the include% features and<br />

some of the <strong>LotusScript</strong> Notes classes.<br />

30 <strong>LotusScript</strong> <strong>for</strong> <strong>Visual</strong> <strong>Basic</strong> <strong>Programmers</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!