default.ivb - What is the best location for the Default VBA Project?

[Anonymous]

Are there best practices for this?

There are a few custom macros that all the users here make use of.

Before, the Default VBA Project pointed to the default.ivb in the local hard drive of each users machine. If there was an addition or update to an existing module, I went through each user's machine and imported the new macro.

After doing this once, I decided to place the project.ivb in the network. I then changed each user's Default VBA Project location to point to the project.ivb in the network. This seemed to be the perfect solution - if I updated or added modules, all the users would have access to it automatically.

A few days later, I realized that when open Visual Basic editor, the project.ivb is set to read-only and if I edit or add modules, it will not be saved.

How can I make the Default VBA Project work on a multi-user environment?

[Anonymous]

I'd like to emphasize that we are in a multi-user environment here. The default.ivb is on the network, and all Inventors point to it.

I opened the VB Editor today, and this time the default.ivb was editable by me. The past few days I was getting a Read-Only when I tried to edit it. What causes this?

Is it possible to have the file as read-only for everyone, and editable only by me?

This has been a mind-bender for the last few weeks. Any help is greatly appreciated.

[Anonymous]

i think it goes read only once someone else has it open (bit like office docs).

i have set the users location to a network drive then once i have a piece of code finished and working i update the network version, otherwise the users are running my dodgey under development code. not sure if this is the best approach but it seems to work ok.

carl