Partial Network Files

[Anonymous]

Sorry this is so long. We have a slightly unique situation within our company and network sharing. What we would like to do is make it so that the database files in the Catalogs folder (default_cat, footprint_lookup, schematic_lookup, wddinrl.xls, etc) and the PLC database (ace_plc) are located on both our network server and locally. The master versions reside on server, and local versions are copies. Users will use the databases on their local machine whenever they are reading from the databases, which is 99% of the time, but whenever they want to add things to default_cat or ace_plc for example, they would add them to the network version, and then people could pull them down to their local copy as needed.

We'd like to keep the icon/panel menu and associated blocks from the libs folder on the server as well and permanently stay there. Users can permanently be pointing there for these files. We don't have issues with those. I think this part can be easily handled with the WD_LIB and WD_PNL vars in all version of wd.env file, which is what we currently do.

I'm having a hard time figuring out the easiest way to do this with the master version editing. We've been using modified wd.env and wd_load.lsp files now for a few years, so I'm moderately familiar with their functioning. For the people that will be allowed to edit the master versions of the catalog and PLC databases, I'm struggling to find a way to make this happen that isn't  a several step process that would be easy to screw up when going back and forth.

My best solution that I came up with right now would be this for the normal setup:

- Have everyone use an appropriately modified wd.env file that exists on their local computer

- This local wd.env file points to the server for the libs, menus, and slides

- No need to specify catalog at all in wd.env or in search path since this could be captured with default support file search path) 

- Have everyone point to server in support path/template settings for title block

I would think that in order to go into "Master DB editing mode", someone would have to do the following items. Keep everything the same as above, but do this:

- rename local wd.env file to something like wd_original.env so acade doesn't find it

- Add support path in acade to server location that contains wd.env file

- Add master PLC db location to support path in acade

- The 'server version' wd.env file is same as local version except that it uses master catalog folder via WD_CAT variable.

Once done editing DBs, do the reverse... rename local wd.env back to normal.. remove the two added support paths.

Then to refresh local parts and PLC db, people would just need to copy/replace the whole "Catalogs" and "Plc" folder from server down to their local machine.

Is this insane? A good idea? Is there a better way?

One way that would be great, but I don't think it's possible, is if it would be possible to keep a project on server at master catalog location and whenever you opened that specific project, it would automatically use the master DBs (default_cat and ace_plc) so that all you had to do was just open that project in order to edit master DBs. All other times ACADE would use your local version. It would be really easy to make sure you were in the right DB in this case.

Side question: is there no way to point to the ace_plc.mdb location other than making the change in the support file search path in options? Nothing in wd.env and or wd_load.lsp that can point to ace_plc.mdb location?

Thank you in advance.

[Anonymous]

(bump)

I've seen some posts on this forum from very knowledgeable people, so I'd like think someone could provide some input.

[ramesh.kambang]

For multiple user environment, ideally, all user should be using the same wd.env file from the common location (server). 

As you mentioned the local wd.env (I am not sure but depends on a company working standard) won't have WD_CAT line. When this line is missing on local wd.env, users won't be able to define catalog details to a component, view catalog details and run a full report, will this be OK?. 

Instead of renaming the local wd.env, can we just add * in front of the line (in the wd.env) to disable that command and remove * to enable the command line?

[rhesusminus]

Have you had a look at using Autodesk Vault?
You can keep a local read-only version of all these files, and the check out/in the databases when you need to have write access to them. Then, the other users can "sync" their local copy of the vaulted files.

[jseefdrumr]

Really....that's a lot of work. Adding paths, removing them, switching env files, only to switch back...you're asking for mistakes to be made, having that many steps in a process.

Wouldn't it just be easier to have everyone working from the same files, and allow only designated users to edit the catalog?

Because honestly, if you think you can get several users to jump through all those hoops you outlined, then they should certainly be able to follow the simple rule of "THOU SHALT NOT EDIT THE CATALOG". Then, all you have to worry about is teaching one or two people how to make those edits, while making sure everyone else has a process whereby they request the edits to be made.

"ONE ENV TO RULE THEM ALL" lol, that's the best way to handle network sharing in ACADE IMO.

[JeffatPrimex]

IMO SQL mode will work best for central control of the default_cat and footprint lookup databases. The other databases and files you should share them as per AutoCAD Electrical then have one or two persons do clean up on a scheduled basis.

Best regards,

Jeff