General information
Category:
Forms & Form designer
>Mike, while I like EVAL() as a much better solution, what's wrong with:
>uValue = CodeList.Code&xCode
Beats me, All I was getting at was Erik didn't need to define the variable before hand, like the sample Macro Substition given. Either way, IMO if you can use EVAL() instead of & you are better off (generally).
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only