Is there a way to get a declared variable to be remembered in another routine?

The concept you are asking about is called a variable's "scope". Here's MSFT's introduction: https://docs.microsoft.com/en-us/off...and-visibility The short answer to your question is decide what scope to give your variable and then structure your project with that scope. Another question is whether to use a single variable with broad scope that many procedures can use or to use multiple procedure level variables and pass the value from procedure to procedure.

I'm not sure we can provide a solid recommendation based only on the code for one procedure. We need to know more about how this variable fits into your overall project and how you intend to use it. I will say that the general rule of thumb is to declare a variable with the narrowest scope possible for what that variable needs to do. Your description suggests that there is only one other procedure that needs this value. If both procedures are in the same module, then maybe dim x as a module level variable.

There's also the question of lifetime (another MSFT article: https://docs.microsoft.com/en-us/off...e-of-variables ), which will get into questions of how long each "call" to VBA is and, therefore, how long x will retain its value. Again, that's probably not something we can provide specific advice for without understanding how all these procedures fit into the overall project.

In your standard module declare a global variable. Note that it should be out side of any sub. Global variable should not be declared in other modules.
Ex:

Option Explicit
Dim x as String
Sub Demo()
'Some code
End Sub

Then you can set x in your Commandbutton1 sub, and x will retain value when used in another sub.