Request for simple code

[Lawsan]

What would the code look like for a visual basic dialog box that had a
textbox or two to enter variables, some buttons to incorporate the variables
into commands for an open console telnet connection (like Reflections or
Exceed)? The command buttons would include carriage returns. In Aspect, I
called these my "Oobie Doobie Do" buttons.

[argusy]

Re: Request for simple code

It would look like a strangely written english poem, not even rhyming, with lots
of lines, some of them indented.
Verses would begin
"Public ....." or "Private ...."
and end with
"End Sub"
carriage returns may, or may not, be recognised by the word "VBCrLf", but I
doubt you'd find them on a command button.
"Oobie Doobie Do", I don't know about - I thought that was a song

Argusy

Lawsan wrote:[color=blue]
> What would the code look like for a visual basic dialog box that had a
> textbox or two to enter variables, some buttons to incorporate the variables
> into commands for an open console telnet connection (like Reflections or
> Exceed)? The command buttons would include carriage returns. In Aspect, I
> called these my "Oobie Doobie Do" buttons.
>
>[/color]

[Lawsan]

Re: Request for simple code

It does look different than the Aspect scripts. Does anyone have examples of
a script that uses a dialog box to communcate with a terminal emulator? I
guess what I am confused by is how the text in a textbox is defined as a
variable and then how to contain that variable in a command line. Visual
Basic code does not look like it reads from top to bottom.
"argusy" <argusy@slmembe r.on.net> wrote in message
news:436FBD20.8 060600@slmember .on.net...[color=blue]
> It would look like a strangely written english poem, not even rhyming,
> with lots of lines, some of them indented.
> Verses would begin
> "Public ....." or "Private ...."
> and end with
> "End Sub"
> carriage returns may, or may not, be recognised by the word "VBCrLf", but
> I doubt you'd find them on a command button.
> "Oobie Doobie Do", I don't know about - I thought that was a song
>
> Argusy
>
> Lawsan wrote:[color=green]
>> What would the code look like for a visual basic dialog box that had a
>> textbox or two to enter variables, some buttons to incorporate the
>> variables into commands for an open console telnet connection (like
>> Reflections or Exceed)? The command buttons would include carriage
>> returns. In Aspect, I called these my "Oobie Doobie Do" buttons.[/color]
>[/color]

[argusy]

Re: Request for simple code

To be a bit more serious about your request....

I haven't gone down this route with VB, using it to communicate with terminals
or emulators, so I can't help you much, but if Dick Grieir is around, he may.
(He writes books on comms with VB)

I get a sneaking suspicion that what you're after is a "dotnet" scenario.
Try asking this in newsgroups with the words "dotnet" or "vsnet" in their name.

BTW, classic VB code does read from top to bottom, but it's all in "packets"
which are controlled by events that are created either by the program's user,
such as clicking on a command button, or tabbing out of a textbox into the next
textbox, or from a trigger (such as a modem wanting to be recognised)

I've yet to even look at a VB.NET (or later version) program - I think I'd be
needing my youth again to understand it

Argusy

Lawsan wrote:[color=blue]
> It does look different than the Aspect scripts. Does anyone have examples of
> a script that uses a dialog box to communcate with a terminal emulator? I
> guess what I am confused by is how the text in a textbox is defined as a
> variable and then how to contain that variable in a command line. Visual
> Basic code does not look like it reads from top to bottom.[/color]

<snip>