I have a system where everything is controlled by security tables keyed
off the userid of the logged on person. I need to change the user variable
to different users to test out the security features.
It does not make sense to change the variable name? Why not just change the
"value" of a variable? This in no way seems to hint that you need runtime
resolution of a variable name. Further, if that data is in tables...then
again all values in a table (recordset collection) can be resolved again at
runtime. So, up to this point...I can not see why having some security
tables controlled by a userID would requite runtime-resolution of variable
names? (you may have some reason...but the simple fact of using security
tables keyed by some user would NOT in any way support your argument). You
are going to have to show an specific example.
I also have many other potential uses for such a tool.
Ok, that may be the case!...but as mentioned, virtually all data, and
properties of collections (built in, or your own custom) can be resolved at
runtime...so, I am still at a loss here.
I'd rather not use debug to do this as I find it a pain to use.
Sure...but no one is suggesting that you do this. If you data is in tables
(as you state), or you store values in collections...both as mentioned can
be resolved at runtime (ie: a value in a value can be used to resolve what
you want). You certainly can't resolve variables in VB at runtime...but as
mentioned developers don't miss this feature since we don't write and design
software that has such a requirement.