Variable within a variable syntax/punctuation?

[smaier]

Hello, all!

What I'm trying to do is use a For/Next loop to reduce the number of lines of code I have by referencing objects with a dynamic name, such as:

For x = 1 To 9
Me.Controls("DimTypeLabel" & x).Caption = "dlkDTL" & x & "var"
Next x

...where DimTypeLabel1 through DimTypeLabel9 are object names and dlkDTL1var through dlkDTL9var are declared variables. The variable x is just being used to rename the object reference and stored variable value each loop.

When I run the above code, the object/label's captions read "dlkDTL1var" through "dlkDTL9var" in the correct objects/labels, but it's not recognizing that what's on the right side of the equal sign is a variable within a variable. It sees it as a variable (x) within a text string.

Is there a proper way to phrase the variable-within-a-variable in this context?



*Edit: minor change for clarity.

[davegri]

Sorry. Reread your requirement and my reply didn't apply so I deleted it.

[Missinglinq]

if you're speaking of var as being the Variable...you need to drop the quotation marks around it:

= "dlkDTL" & x & var

not

= "dlkDTL" & x & "var"

the quotes tells the Access Gnomes that var is a String...not a Variable.

Linq ;0)>

[smaier]

No worries, davegri. I edited my post to hopefully clear up my bad phrasing.

[smaier]

if you're speaking of var as being the Variable...you need to drop the quotation marks around it:

= "dlkDTL" & x & var

not

= "dlkDTL" & x & "var"

the quotes tells the Access Gnomes that var is a String...not a Variable.

Linq ;0)>

Thank you for the reply, Missinglinq!

Actually, the declared variables are dlkDTL1var, dlkDTL2var, dlkDTL3var, on up to dlkDTL9var. The loop variable x is in place of the number in the middle of the variable.

I'll try with no quotes at all but I thought it would see dlkDTL, x, and var as 3 separate variables.

[smaier]

Update;

With no quotes it did indeed read the not-in-quotes strings as individual variables (variable not defined error).

I could just change the variable names so the number is at the beginning or end instead of the middle which would work. Or I could just type out all the lines of code individually, dropping the For/Next routine. Just seemed like a slimmer and easier to troubleshoot solution. It would just bug me not knowing if I was asking the impossible or just unable to figure it out.

I do appreciate the help!

[Micron]

This

what's on the right side of the equal sign is a variable within a variable

I just don't see. I'd expect the caption would be "dlkDTL1var" for example. As coded, var is a string, not a variable as was pointed out. Perhaps if you show more of the code, because var is somewhat ambiguous. An expected result would also help.
If the labels are attached, I'm wondering if it would be far simpler to refer to the control's only default member, which is the label, and is referred to as .Controls(0) instead of worrying about referring to the control and it's label as separate entities. Don't know because the whole intent/purpose isn't clear, and what you're calling an object should probably be referred to as a control for clarity.

[smaier]

Hello, Micron. Thank you for the reply.

I took your suggestion and have attached a database example. Hopefully this will make up for my inability to properly describe what I'm trying to accomplish code-wise. There's no table. Just a form with some controls and a module declaring variables.

The short description is I'm trying to reduce 9 lines of code down to one (if you don't count the For/Next lines). If it's possible, this would allow me to apply the method on other forms, reducing the number of lines from ~200 down to maybe a dozen or so.

Thanks again!


Example1.accdb

[Micron]

If I understand what you're trying to code, then you cannot. Notwithstanding that your reference
Me.Controls("DimTypeLabel" & x).Caption = dlkDTL & x & "var"

is sort of backwards because it probably should be

Me.Controls("DimTypeLabel" & x).Caption = dlkDTL & "var" & x or just

Me.Controls("DimTypeLabel" & x).Caption = dlkDTLvar & x

because your construct is dlkDTLvarx where x may be dlkDTLvar5. You're trying to put the var at the end when it's supposed to be in the middle.

Regardless, you are trying to define constants such as dlkDTLvar9 and those constant names are as you have named them. I doubt that you can refer to them directly by a partial name and make it work just because you're tacking a number onto the end. Trying to refer to the constant as dlkDTLvar & x (where x is e.g.5) will create a string as "dlkDTLvar5". IMO, only if you could pass that string to the name property of something might this work, but I don't know what would hold that name property when you're dealing with constants. I'm not aware of whether or not a constant has a Name property and would have to look that up.

I'll look at your db to see if I have another suggestion.

[June7]

Cannot dynamically build VBA variable names. Perhaps you should use an array to save these 9 values then dynamically reference array element.

[Micron]

If we knew why this was needed we might be able to provide a simple solution. On my phone, so maybe I missed that?

[ssanfu]

Or consider using a table to hold the values. Open a record set and do the looping. Plus it is easier to add/edit values than editing arrays (don't have to edit code).

[smaier]

Thank you so much for the replies, guys!

From what it sounds like, and which would actualy make sense (as June7 stated), you cannot dynamically build variable names in VBA. Not that big a deal as the only benefit I was chasing was limiting the number of lines of code used. Previously I have used this method when referencing controls dynamically with the same For/Next scheme when the control names allowed for it, usually when they were the same name with numerals at the end or wherever. At one point recently I thought to myself "Yaknow, that would be pretty cool if I could do the same with variable names!" and started the process of banging my head against the wall in hopes that could somehow make it work.

As far as the function/work the code is doing, the database I posted earlier is but a small part of a larger group of forms that get filled out for dimensional inspections, most of which are, at the output side, highly repetitive. One sequence of input text boxes and 45 labels and textboxes that show the same things across multiple forms. This would lend itself to using an array as was also mentioned. This is probably the best solution for me as it stands as I could really use some practice on working with the values stored. I've only used an array in one other working project and it was very simple by comparison.

Thank you for the replies and input, all! I feel a bit better knowing it wasn't working because it's not possible, rather than because I'm not capable of figuring it out.

[Micron]

If you made them textboxes you could probably could call a function and pass the textbox name or Tag property for example, thereby setting its value in the function. One little snippet of code, I'd say. The function could accept a string (which you then process accordingly) or the literal value, in which case you could do away with the constants altogether. In place of the constants or an array, you'd need to identify the function parameter in the textbox source property somehow. Same amount of coding I'd say, but at least it should work.

[smaier]

Hi Micron.

That's an interesting suggestion. A bit more complex than I am accustomed to but that's a good thing. Shows a method that could offer more possibilities than my original approach.

Again, thank you all for the answers and suggestions!