Using Perforce for FM version control?

[Simon Bate <sbate@xxxxxxxxxxxxx>]

Our current version control tool (good faith) doesn't seem to be working
well, so we're looking into some alternatives.  Because our engineering team
recently shifted from SourceSafe to Perforce, we have a choice: use the
existing licenses for SourceSafe and manage it ourselves, or purchase
additional Perforce seats for our team and have it managed by the same folks
who are managing Perforce for engineering. 

The reviews of using SourceSafe to version control FrameMaker and WWP (.wdt)
files are mixed.  I've only had one bad experience with SourceSafe
corrupting a WWP file, but others in our team have reported a number of
FrameMaker file corruptions.  

The question: is anyone out there using Perforce for FrameMaker/WWP version
control?  If so, what has your experience been?  Have you ever experienced
corruption of FrameMaker files? WWP files?

Any input would be useful.
Thanks,
Simon  

v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v
Simon Bate
Online Visionary, Publications
Extricity, Inc.
v  650 486 4477
m 408 396 7947
v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v

Proprietary and Confidential Information. The information transmitted is
intended only for the person(s) or entity(ies) to which it is addressed and
may contain confidential and/or privileged material. Any review,
retransmission, dissemination or other use of, or taking of any action in
reliance upon, this information by persons or entities other than the
intended recipient is prohibited. If you received this in error, please
contact the sender and delete the material from any computer. 



** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **