Static variables with variable names

[Jerry Spence1]

Sorry for the confusing title - not quite sure what I'm after here.

I think need to have a static variable in a procedure, but the name of that
variable will be designated at run time. Also I don't know how many
variables I need until run time either!

Just to explain, I have a number of IP based door access control readers and
I need to retain a status flag about certain ones - I don't know which ones
until run time. The readers have names. So I might have:

static <my variable> as boolean

which will come out as static Reader_30 as boolean

There may be another way of doing this of course, such as properties.

-Jerry

[m.posseth]

well in this situation i would create a structure that holds the required
info about the status ( boolean , string , integer values about the status
etc etc )
then store these structures in a hashtable or collection ( i prefer the
hashtable as it is the fastest )

now you can save these values with anny name you like , and can even check
for there existence in the lookup table

i could write you an example if you like the idea

regards

Michel Posseth


"Jerry Spence1" <je**********@somewhere.com> wrote in message
news:43***********************@ptn-nntp-reader04.plus.net...

Sorry for the confusing title - not quite sure what I'm after here.

I think need to have a static variable in a procedure, but the name of
that variable will be designated at run time. Also I don't know how many
variables I need until run time either!

Just to explain, I have a number of IP based door access control readers
and I need to retain a status flag about certain ones - I don't know which
ones until run time. The readers have names. So I might have:

static <my variable> as boolean

which will come out as static Reader_30 as boolean

There may be another way of doing this of course, such as properties.

-Jerry

[Jerry Spence1]

I think I like that idea - but am not very knowledgable on it. If you have
an example I'd be grateful

-Jerry
"m.posseth" <mi*****@nohausystems.nl> wrote in message
news:eY**************@tk2msftngp13.phx.gbl...

well in this situation i would create a structure that holds the required
info about the status ( boolean , string , integer values about the status
etc etc )
then store these structures in a hashtable or collection ( i prefer the
hashtable as it is the fastest )

now you can save these values with anny name you like , and can even check
for there existence in the lookup table

i could write you an example if you like the idea

regards

Michel Posseth


"Jerry Spence1" <je**********@somewhere.com> wrote in message
news:43***********************@ptn-nntp-reader04.plus.net...

Sorry for the confusing title - not quite sure what I'm after here.

I think need to have a static variable in a procedure, but the name of
that variable will be designated at run time. Also I don't know how many
variables I need until run time either!

Just to explain, I have a number of IP based door access control readers
and I need to retain a status flag about certain ones - I don't know
which ones until run time. The readers have names. So I might have:

static <my variable> as boolean

which will come out as static Reader_30 as boolean

There may be another way of doing this of course, such as properties.

-Jerry