Multiple users on network VBA (.ivb)

[Anonymous]

Quick question. How do I have multiple users have the same VBA and still retain the ability to modify it? When I have two or more users loading the .IVB file, it disallows edits or saves to it on my end. Is there a simple solution to this?

[WCrihfield]

I have mine located on a network drive.  All other users are set up to reference that same ivb.  But I'm generally the only one doing any editing to it.  It's been this way for a couple years.  We don't  have any problems, thus far.  It seems normal that it would only allow one person to edit it at a time.

How are you sharing the file?  Do you have Vault?  Are all users referencing the same Project file. If you don't have Vault, you can still set the Project file up as a Vault style Project, which allows several sharring options.

[CadUser46]

My company uses this exact setup and has done for many years.  This is how i structure it.

1. Network share where users have read access, i have modify rights.  You or IT will need to make a new share probably and set the access rights on it.  This is what will be tripping you up.

2. We have a standard ApplicationOptions.xml and UserCustomization.xml that users apply at initial setup.  The app options file path sets the path to the Default.ivb(modified) on the network but i also have them go in and manually browse so they can tick the 'Open VBA read only' tick box (i forget wording, could be Open *.ivb Read Only).

I could modify the shared Default.ivb but actually i keep an entire other master copy of all the styles, standards, templates, ivb in another location which i modify under a different project.  I then sync the changes to various network shares.  Works fine on a 50 user setup.

[Anonymous]

I do not have vault. The file is located on our network drive. As of right now, only I am using the VBA file. I did have another user test out what would happen when referencing the same file (I basically have on startup code that switches them to that path) and this is the error I get when more than one use the file at the same time.

[CadUser46]

I generally wouldnt recommend switching the ivb file after startup.  Set the path in app options then restart IV.

[WCrihfield]

Is your Project file located at or above that directory on the network?

I have a folder named Macros, which is located below my Project file on the network.

My .ivb file, and all of my Macros are located within this folder.

We do not have Vault either, but we set up our Project Type as Vault, instead of Single User.

All users are referencing the same Project file, Appearance Libraries, Material Libraries, and .ivb file.

We do not specify anything under "Included file", or under "Workgroup Search Paths", or under "Workspace", or under "Libraries", or under  Vault Options.

We do have the Appearance Libraries, Material Libraries, Frequently Used Subfolders, Folder Options set up.

Also under Options, we have Old Versions To Keep On Save, Using Unique File Names, Name, & Shortcut set up.

But we did not specify Owner or Release ID.

It has been a fairly nice sharing arrangement amongst the users at our company for the last couple of years.

[CadUser46]

Well, it sounds like you're on the right track but i'd make some adjustments.

1. Whether you're editing cad files directly off the network is a different story but i dont believe should have any bearing on the ivb.

2. I would not use a Vault project if not using Vault.  Change to single user although my experience of multi-user single project is quite dated so i cant be sure on this one.  Is that what you're doing?  No other PDM system or local files on each machine?

3. I personally keep appearances, styles, templates, design data, macros in their own folders outside of and at the same level as the cad data.  I know Vault projects force some things to be inside the project path but from the sounds of it you dont need this.

4. The ivb is not determined by project, it's by App Options > File > Default.ivb path.  I also configure Templates and Design Data here as good practice as in older versions of Inventor things like the thread.xls did not take its priority from the project.

If you want to DM me i have a little time to skype.

[CadUser46]

lol, just realised i replied to wrong person.

[Anonymous]

First, I'd like to clarify I dont set the paths on startup for every instance, just the first time setup, or an update if needed.

Would it be possible to program the VBA file (.ivb) to read only in ilogic?

Right now I have a setup batch file that sets the XML paths, and then runs a setup .iam which executes some startup code setting paths, and whatnot. During that setup, I have these lines of code in iLogic 

ThisApplication.FileOptions.DefaultVBAProjectFileFullFilename = "\\...\StandardTemplates\VBA_MAIN.ivb"
InventorVB.DocumentUpdate()
InventorVb.RunMacro("ApplicationProject", "AutoSetup", "FirstTime")

 Is there a way I can set the default VBA Project Path as Read only in iLogic? Or is there some better way I can go about this. Doing what @CadUser46  would be idea, but setting it manually would be not-so ideal if I can avoid it.

Thank you, 

[CadUser46]

I'm guessing you figured out how to call the IV app and pass in the file as a variable in the batch file, then relying on iLogic trigger to run the code? like C:Program Files\...\Inventor.exe "setup.iam"....run on open.

In my experience it's always better to apply path settings prior to launch, or at least force a restart of the app.  As such for the initial setup i use a powershell script to apply all the registry settings i want (paths, workspaces, folder creation, project copy etc).  This only gets run once per machine and windows profile.  If you're allowed to run unsigned code you can just import a .reg (modified to suit and just containing the content in HKLM\software\autodesk\version etc).  In fact you dont even need a script, the user could just double click on your .reg file.

NOTE:  I believe there are extra things inside the xmls that are not addressed in the registry hence i always instruct users to reimport the xmls anyway but i guess you're trying to automate this step.

I dont believe it's possible to make it read only in that manner.  The first machine to launch Inventor, that has modify access to the file path will reserve modify access to it (even if they ticked the open vb read only box).  Everyone else is read only.   Hence why it's better to control access rights at the network level.

You could at the very least enable password protection of the ivb file from within the IDE. It's good practice anyway in case you have any credentials stored here for things like service accounts.

I think it's under tools somewhere.  They wouldnt be able to modify the code but would be able to save it.

Since you have access to the server you could try right clicking on the file and directly modifying the security.  I've never tried.

While you're on the topic of protection i'd be equally concerned about users have modify access to the styles library.  Overwriting one ivb file with a backup copy is easy.  Unpicking all the changes to the styles library without a backup may not be.