By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,790 Members | 1,398 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,790 IT Pros & Developers. It's quick & easy.

Declaring variables

P: n/a

Hi guys.

I have a question about declaring variables. I do a lot of re-querying
of controls in my database and I use the Set statement with a variable
set to the name of the control to tell the program which control to
requery. This makes it easy to requery controls on a different form.
However, up until today, I was dimming a new local variable for each
control I wanted to deal with ( E.G. Dim cbxctl as control) and then
setting that variable to the control I wanted to work with.

This works fine but it can be messy because you are dimming new
variables all over the place in your code. I thought it might be better
to declare all my variables in a global module. this cleans up the code
but it creates the problem that if I forget to use the set statement I
could end up updating the wrong control, unless I remember
to set each ctl to nothing.

Am I on the right track or should I stick to local variables.

thanks guys

Colin

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Your original idea was right.
Declare your variables with the narrowest scope possible, so they do not
interfere with each other.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"ColinWard" <je*********@hotmail.com> wrote in message
news:41**********************@news.newsgroups.ws.. .

Hi guys.

I have a question about declaring variables. I do a lot of re-querying
of controls in my database and I use the Set statement with a variable
set to the name of the control to tell the program which control to
requery. This makes it easy to requery controls on a different form.
However, up until today, I was dimming a new local variable for each
control I wanted to deal with ( E.G. Dim cbxctl as control) and then
setting that variable to the control I wanted to work with.

This works fine but it can be messy because you are dimming new
variables all over the place in your code. I thought it might be better
to declare all my variables in a global module. this cleans up the code
but it creates the problem that if I forget to use the set statement I
could end up updating the wrong control, unless I remember
to set each ctl to nothing.

Am I on the right track or should I stick to local variables.

thanks guys

Colin

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.