Command Button - Visual Basic Problem

[RuralGuy]

The advantage of using the method described by Paul (PBaldy) is that it avoids those public variables and isolates *all* of the code in the receiving form. No mysteries for someone new trying to support the system. I've personally never had a problem using bound controls on a form. Just my $0.02!

 

[DaveCollins181]

Thanks RG, I did download the sample DB from PBaldy so will try to replicate on my DB. I didn't get much of a chance to try today as it was busy in the office. I'm aiming to get the DB working by the end of next week so hopefully it will be ready to roll. Thanks for everyone's assistance. Dave

 

[Libre]

The advantage of using the method described by Paul (PBaldy) is that it avoids those public variables and isolates *all* of the code in the receiving form. No mysteries for someone new trying to support the system. I've personally never had a problem using bound controls on a form. Just my $0.02!

Every method has its strengths and weaknesses.
If you have a lot of users then it's true that global variables can get you into trouble. But there are ways to avoid the troube.
You can reinitialize them the moment after they "carry" the value to the control you want to write to.
I would prefer to deal with the back end as much as possible than use bound or even unbound controls on a form. Much faster, for one thing (I believe). You can also design functions that send the variables as an argument and that would *pretty much* isolate that variable for the receiving form. But if writing to a bound control works for you, then write away. There's always more than one way to skin a cat, as they say.

 

[RuralGuy]

I agree, if it works for you, then use it.