USING AN .xla FILE TO STORE MACROS

[Chuckles123]

Our OS is WXP-Pro. We are using an .xla file on a shared network driv
to store macros. As a backup, I am "trying" to keep a matching .xl
file on my local drive. Also, to make changes in the VBA Code withou
executing the macros, I have to be able to open the file, obviously.

I'm probably crazy, but it seems like I am getting inconsistent result
when saving code changes. This is the procedure I use: when gettin
undesired results in the spreadsheet, I will "step-thru" the code, fin
and correct the mistakes, and then click-on the "Save" icon in th
Editor; I then shut down the Editor, and click-on the "Save" icon i
the spreadsheet -- herein lies the rub, apparently, the code change
just made are sometimes not saved in my .xls copy of the shared .xl
file.

I have been using the same prefix for the shared .xla file and my loca
.xls file -- I am thinking about making them different.

Help

 

[Celtic_Avenger]

Just a thought......

remeber that some of the macros may be pointing and executing code
from the copy in the shared drive and not soley in your local drive.

Ensure that if there are any address's within the macros, that they no
point to your local drive, not the shared one

 

[Bob Phillips]

Chuckles,

You don't have to keep an xls copy. You can open an xla file in Excel just
as you can an xls file. Just make sure you uninstall the add-in before
opening it. The file won't be visible in Excel, but you cane edit the code
in the VBIDE as normal.

As for keeping a copy on your local drive, surely your network drives are
backed up, so there is no need? I keep many add-ins at work on a network
drive, and keep development versions on there which I update and then
promote to production. Never any problems.