Prev: Calling insertion stored procedure using ADODB.Command
Next: Two graphics problems
From: Jeff Johnson on 21 May 2010 11:20
"Dee Earley" <dee.earley(a)icode.co.uk> wrote in message
news:%23Zd1WTM%23KHA.208(a)TK2MSFTNGP02.phx.gbl...

> Well I never, been using the language for 15+ years and I never noticed
> that keyword...

It was available in pre-visual versions of BASIC as well. If not that exact
keyword, at least the functionality. I know I could explicitly raise an
error in TRS-80 Color BASIC.


From: Dee Earley on 21 May 2010 11:58
On 21/05/2010 16:20, Jeff Johnson wrote:
> "Dee Earley"<dee.earley(a)icode.co.uk> wrote in message
> news:%23Zd1WTM%23KHA.208(a)TK2MSFTNGP02.phx.gbl...
>
>> Well I never, been using the language for 15+ years and I never noticed
>> that keyword...
>
> It was available in pre-visual versions of BASIC as well. If not that exact
> keyword, at least the functionality. I know I could explicitly raise an
> error in TRS-80 Color BASIC.

Yeah, I was on QBasic before that and that predated my knowledge of
proper error handling or structured coding :)

--
Dee Earley (dee.earley(a)icode.co.uk)
i-Catcher Development Team

iCode Systems

(Replies direct to my email address will be ignored.
Please reply to the group.)
From: Tony Toews [MVP] on 21 May 2010 16:55
Dee Earley <dee.earley(a)icode.co.uk> wrote:

>> If lrc<> ERROR_NONE Then Error 5
>
>Well I never, been using the language for 15+ years and I never noticed
>that keyword...

Glad to read I'm not the only one. <smile>

I replaced the Error 5 line with a Goto Exit routine.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
First  |  Prev  | 
Pages: 1 2 3
Prev: Calling insertion stored procedure using ADODB.Command
Next: Two graphics problems