I recently has a situation where I had to prematurely close an accde file. This closure left a number of tempvars on the system.
My opening sub checks for the existence of one such tempvar to either run the startup routine or go straight to the main menu.
The result was that the main menu was opened incorrectly, and inoperative, and the program was again shutdown prematurely. Long live the tempvars.
Ultimately temporarilyI used tempvars.removeall at the beginning of the startup sub and the softwre ran as expected.
Question.
Is there a way to eliminate tempvars other than via access vba?
I have been using tempvars for some time, now with great success. As this is the first negative encounter I have had, I will continue to use them because, IMO, their benefits far outweigh any downsides.
My opening sub checks for the existence of one such tempvar to either run the startup routine or go straight to the main menu.
The result was that the main menu was opened incorrectly, and inoperative, and the program was again shutdown prematurely. Long live the tempvars.
Ultimately temporarilyI used tempvars.removeall at the beginning of the startup sub and the softwre ran as expected.
Question.
Is there a way to eliminate tempvars other than via access vba?
I have been using tempvars for some time, now with great success. As this is the first negative encounter I have had, I will continue to use them because, IMO, their benefits far outweigh any downsides.