yang686526

macros locked by users?
we put our macros on the network for the users to run. when we make changes we need to update the macros but they seem to be locked by the first person that opened them and we can't overwrite them. is there a way around this? should macros be loaded locally on the c drive? what do other company's do?
yup stinks. they cannot unload the macros either, they have to close sw before you can get access to it.
i think you have two choices, make the macros read-only...then you change the read only state before you edit it, or copy the files to their c:, which is what i do, but you need a way to update the macros if you make changes.
jeff sweeney, cswp
sw user since '96
they can unload the macros. on the computer that first loaded them go to tools->macros->edit... and select any macro to edit. this will open up vbe showing all of the macros the machine has opened. just close vbe down once it opened and problem solved. but yes, pain in the badside
to expand on what jeff said:
we have macros on the network. they are in two directories, one for usable macros, and one in a working directory. the macros in the usable directory are all read only, that way anyone (and multiple people at the same time) can open them up. if you need to edit a macro, copy it to the working directory and edit it there.
charles culp, cswp
aerospace design engineer
essex industries - st louis, missouri
sw2009 sp2.1
thanks for the replies.
so if the file are properties on the macro's are set to read only, sw doesn't lock them to the users and i can overwrite them?
nope it will still lock them. you can unlock them by doing what i said though.
there is a live workaround too: while you cannot edit the files while locked, you can change their folder name! this allows for a sneaky little trick that doesn't require going to the offending computer.
simply rename the folder on the netword drive where the macros are located. then copy that folder to the same drive. rename the new folder to be the same name as before the original folder was renamed.
the macros in the old folder with the changed name will still be locked out, but the macros in the new folder with the original name will be free to edit!
matt lorono
solidworks 2007 sp3.1
cad engineer/ecn analyst
i've seen this problem. in each macro, are the declarations before sub main or after? moving the declarations after sub main fixed this problem.
example:
problem present:
dim swapp as object ' declaration before sub main
sub main()
set swapp = application.sldworks
end sub
problem not present:
sub main()
dim swapp as object ' declaration after sub main
set swapp = application.sldworks
end sub
i don't know exactly why. my guess is that when the declaration is made outside the sub they are left out there even though the macro has ended, but if the declarations are inside the sub they are released at end sub.
try it and let me know.
kevin kenny, cswp
sw 2009 sp3.0
hp xw4300
quick