We've been using Version Cue CS2 for about 18 months, and it works quite well for us. We're an in-house department with 5 designers, and we create packaging, catalogs, web site, manuals, and VC is ideal when different people work on the many of the same projects.

Basically our projects are named with the model number of the product.
We have a project named "Work In Progress", with each person having their own folder to save work that hasn't been given a model number yet.
Previously most of us kept that type of work on our respective machines, which makes it inaccessable to anyone else that might have to work on it.
We also have a Project called Standards, which has "standard" artwork for each of our brands such as logos, warranties & legal text.

Due to the nature of our business change is normal, so is returning to the original! This is where VC shines. Keeping comments on the changes/versions helps big time, and not just for the designer picking up a project. I don't know how many times I've opened a file and couldn't for the life of me remember creating it, until the comments I left reminded me.

As far as Bridge is concerned, just think of it as Finder on steroids. It may seem like a lot of work at 1st, but once you get your head around it you'll be using Finder less and less. It's not really work, it's just different from what you're used to. In the end it's just mouse clicks anyway.

I just checked out some podcasts for VC & Bridge CS3 and there's a big improvement over CS2. It seems to be much more intuitive to use than CS2.
Well I gotta get back to work, but if you have any other questions just ask.
I'm in Eatontown, NJ BTW.
Have a Nice Weekend!
Gene

We deployed CS2 version on all our Macs (18+) and I had n end of horrors. . . wrong versions being saved. . .HUGE folders with nothing in them in the documents folder having to hope and pray that the LAST version didn't overwrite another one. . . and Bridge was just sticky and always had problems with some script or the other. Lets not even start about how to BACK up the files VC's admin set up was just to lame when it came to backing it up right (no incremental back ups and rollbacks)

Then I realised! We weren't using it on a SERVER! DUUUHHH If it was on a dedicated server it would have worked better (I think since I don't have a server to put it on)

Roadmaster I would LOVE to hear more about you implementation of VC in your environment. Is it running on a server and what kind.

thanks

"Try not, Do! or do not, there is no try."
-Yoda

Are the above mentioned system very different from using Subversion ?

I am coming from a developers perspective and have used subversion or CVS for many years. Would these not be adequate ? They offer comprehensive tools for diff'ing, multi-users, roll-back, web interface etc. They can be accessed through ssh, web, apache etc.

There are quite a few GUI interfaces on Mac and Windows.

I use a Mac program called Zig Version which works well.

On Windows Tortoise SVN is very good. (I wish it was available for Macs.)

What does VersionCue do that subversion does not ?

Will

--
http://www.macscan.net/

We have VC installed on a PC server, but we all have Macs.
The reason for this is, that's we had available to us so we didn't have to purchase any new hardware. The PC version of CS2 we installed on the server was from when we all were working on PCs.
When we installed VC on the server, we created a Workspace where all of the shared projects will be created.
When you install VC on each persons machine there is a workspace created locally, each person can create their own Projects, then choose to share them or not.
When you create a Project for everyone to access, it needs to be created on the servers Workspace.
Our IT guy backs up all of the servers we have, so that includes the VC Workspace.
To access a Project created on the VC server.
1. Open bridge and select VC in the favorites pane on the left side.
2. Open Workspaces which is shown on the right.
3. Select the Workspace you created on the VC server.
Once you have opened the VC server Workspace you can access any projects in there.
VC copies any files or folders in the project locally to the documents folder on your machine. NEVER alter any files in the VC folder in the documents folder.
The next time you select VC in bridge, the projects you have opened/accessed on the VC server Workspace will be displayed. Projects you haven't accessed will not be displayed.
The projects in the VC server you have accessed will always be shown when you choose VC in select VC in Bridge.
You must disconnect from the Project for it not to be shown in VC. Once you disconnect VC deletes the local copies. You must empty the trash on the Local machine to re-claim any space on the hard drive though.
Well that's the basics of our configuration.
If you have any other questions, just ask.
GEne

I email you?
Absolutely my e-mail address is
I believe the IT dept created a virtual server for the VC software and Workspace on our server.
The only problem I've really had was when my user account on my G5 tower became corrupt. I called Adobe and we were able to troubleshoot it in less than 1/2 hour.
Gene

Is this a server setting? If so I'd have to ask IT.