Is sharing variables between different VBA code executions reliable?

charvatk

New Member
Joined
Feb 6, 2014
Messages
6
Hallo, as I noticed, variables, which are declared as public, or on the module level are preserved after finishing VBA code execution, and they are kept in memory until workbook is closed, some error occurs etc..
I’m working on project, where it is necessary to keep some values of variables, and use them in next code execution (without closing workbook).
Is it safe to use variables stored in memory from previous code execution, or it’s safer to save values into some range and read them from the range during next code execution?
I need various kinds of variables in the project, user defined classes, collections, etc..
Thanks,
Karel
 
Welcome to the Board!

I would probably error on the side of caution and store the values somewhere in a range of my workbook. Seems to be the safer option.
 
Upvote 0

We've detected that you are using an adblocker.

We have a great community of people providing Excel help here, but the hosting costs are enormous. You can help keep this site running by allowing ads on MrExcel.com.
Allow Ads at MrExcel

Which adblocker are you using?

Disable AdBlock

Follow these easy steps to disable AdBlock

1)Click on the icon in the browser’s toolbar.
2)Click on the icon in the browser’s toolbar.
2)Click on the "Pause on this site" option.
Go back

Disable AdBlock Plus

Follow these easy steps to disable AdBlock Plus

1)Click on the icon in the browser’s toolbar.
2)Click on the toggle to disable it for "mrexcel.com".
Go back

Disable uBlock Origin

Follow these easy steps to disable uBlock Origin

1)Click on the icon in the browser’s toolbar.
2)Click on the "Power" button.
3)Click on the "Refresh" button.
Go back

Disable uBlock

Follow these easy steps to disable uBlock

1)Click on the icon in the browser’s toolbar.
2)Click on the "Power" button.
3)Click on the "Refresh" button.
Go back
Back
Top