Re: Pass locatioin to Secondary Form
- From: "Ed Bitzer" <edbitzer@xxxxxxxxx>
- Date: Sat, 14 Jun 2008 17:30:29 -0400
Joe,
Rereading my comment to you I see some lack of clarity - I did mean
that I am going to avoid the globals and already have recoded a couple
of older programs I wrote for myself using "properties" (fields) in a
class and dumped the module.
Thanks again, Ed
"Joe Cool" <joecool@xxxxxxxx> wrote in message
news:4sq554dbvmrm6gj97utg8c6lestna8fjih@xxxxxxxxxx
On Fri, 13 Jun 2008 07:03:03 -0400, "Ed Bitzer" <edbitzer@xxxxxxxxx>
wrote:
Thanks Joe... this lets me concentrate on me using added classes to
avoid my historical use of globals and modules and maybe learn to
use
them more often.
If you ever expect to move to C#.NET, you will be forced to give up
on
global variables.
"Joe Cool" <joecool@xxxxxxxx> wrote in message
news:t17354hjjt66hmg1hhohrthsma75bhnc2l@xxxxxxxxxx
On Thu, 12 Jun 2008 17:11:36 -0400, "Ed Bitzer"
<edbitzer@xxxxxxxxx>
wrote:
Appreciate some direction as to what most of you professionals do
when
passing some limited variables to another form. A simple example
would be passing the location of a second form. I could use a
constructor which I think of as parameters attached to the
creation
of
my New form (parameters) or I could use "properties" as I have
learned
to use with classes. Some advice please.
My personal preference is to use properties in the secondary form
to
pass data to it from the calling form.
.
- References:
- Pass locatioin to Secondary Form
- From: Ed Bitzer
- Re: Pass locatioin to Secondary Form
- From: Joe Cool
- Re: Pass locatioin to Secondary Form
- From: Ed Bitzer
- Re: Pass locatioin to Secondary Form
- From: Joe Cool
- Pass locatioin to Secondary Form
- Prev by Date: Re: When does the Finalize event of a class fire?
- Next by Date: XML Comment Screwed - Possibly a bug in VB??
- Previous by thread: Re: Pass locatioin to Secondary Form
- Next by thread: SAP VB.NET connection
- Index(es):
Relevant Pages
|