Release Notes for
P4OFC, the Perforce Plug-In for Microsoft Office
P4OFC, the Perforce Plug-in for Microsoft Office, integrates
Perforce with MS Word, Excel, Project and PowerPoint.
For details about using P4OFC, refer to the on-line help file
by choosing Perforce>Help from within your Microsoft Office
application. To uninstall P4OFC, run the P4OFC installer
(p4ofc.exe) and choose the Uninstall option.
P4OFC is compatible with 32-bit Microsoft Office
2010/2007/2003/2000/XP on Windows 2000/XP/Vista/7.
Perforce Server compatibility
You can run P4OFC with Perforce Server versions 2001.1 or later.
Major new functionality in 2007.3
Keyword expansion - job009850, job012942
P4OFC can now expand RCS keywords using custom
properties inserted into fields in Microsoft Word
documents. This feature aids document identification.
Document fields can be included within the document
or within headers or footers. For details, refer to
the P4OFC online help. The custom properties may also be
added to Microsoft Excel, PowerPoint and Project for
identification. For details, refer to the P4OFC online help.
Suppress attempts to connect when server is down -
If P4OFC cannot connect to the server, it now prompts
you to specify whether it should continue to try to connect.
This feature enables you to avoid the delay caused by
Enhancements for Checked Out Documents dialog - job007674
This dialog now includes an Open button, enabling you
to open another document by double-clicking it or by
selecting it and clicking the Open button. Once
opened you can Revert (Undo) the Checkout.
Bugs fixed in 2007.3
Check-in on Save now works with new Powerpoint 2007 document.
P4OFC now displays the lock icon for +l files and files that
were locked manually.
Get Latest Revision: dialog heading corrected from "Open
from Perforce" to "Get Latest Revision".
Excel no longer crashes when opening a file from a CD
drive and then closing it.
Fixed occasional Word crash that occurs right after
check-in or when entering password using slow dialup.
P4OFC now recognizes exclusively locked files.
Error no longer occurs when diffing a file that has a
read-only attribute set on it in Word.
"Check out on open" fixed for Microsoft Project.
Fixed application error that occurred when adding a file
to Perforce using Microsoft Word.
Installing "Check out on open" macro for Microsoft Project
To provide the "Check out on open" for Microsoft Project,
P4OFC requires you to manually install a macro by double-clicking
the p4project-install.mpp file, which is installed when you
install P4OFC. Microsoft Project might require you to
lower your security level to install the macro.
This step is optional -- if you don't install the macro,
the functionality is not available in Microsoft Project
(all other P4OFC functionality remains active).
Note that, if you uninstall P4OFC, you must manually
uninstall the macro. To uninstall the macro, double-click
the p4project-uninstall.mpp file
Forward slashes in client root paths
Windows paths are properly delimited using backslashes, but
Perforce does not prevent you from using forward slashes when
configuring this settings. Such paths can cause P4OFC to crash.
New features in 2005.1
* Open from Perforce
To retrieve a file that is in your depot but not in your workspace,
choose Perforce>Get Latest Revision from Perforce.
* Microsoft Project support
* Secure server support
P4OFC now handles connections to secure mode servers, and prompts
for password as required
* Options dialog layout and verbiage improved
The options are more clearly grouped using a tabbed format.
Support for a "Check-in on close" option has been added.
* Don't edit ktext files with Word
If you edit and submit a ktext file using Word and P4OFC,
you'll see error messages like the following:
"unlink: c:\depot\myktextfile.txt: The process cannot access
the file because it is being used by another process."
Use text editors and the P4 or P4Win clients to manage ktext
* Incompatible with Test Director macro
P4OFC has a known incompatibility with Mercury Interactive's
TestDirector QA suite, when the Test Director Word macro
template is used. If you install P4OFC on a machine where
the Test Director Word macro template is also installed, Word
might crash during P4OFC operations. To fix this problem,
delete and recreate the Normal.dot Word template.
* Don't uninstall with Office applications running (job008973)
If you want to uninstall P4OFC, close Microsoft Office
applications before doing so, to prevent the applications
* Don't open embedded graphics files while editing Word files
Word might crash if your document contains embedded graphics that
are also open in the graphics editing application.
* Spurious checkout prompt when printing from Windows Explorer
If you have P4OFC checkout prompting enabled, P4OFC might displays
a checkout dialog when you right-click a file in Explorer and
Workaround (to supress macros when printing):
1. In Windows Explorer, choose Tools>Folder Options and click the
File Types tab.
2. Click the Office filetype you want to change (for example .doc), then
click the Advanced button. The Edit File Type dialog is displayed.
3. Double-click Print. The Editing action dialog is displayed.
4. In the Application used to perform action field, append the /a
C:\Program Files\Microsoft Office\OFFICE11\WINWORD.EXE" /x /n /dde /a %1
5. Click OK to dismiss the dialog, then close the Edit File Type and
Folder Options dialogs.
Bugs fixed in 2005.1
P4OFC now displays the correct date and time in the 'Last modified
in depot' field.
P4OFC no longer displays an error message when you click No in
response to the "Track Changes?" prompt.
P4OFC now handles missing client settings.
Excel no long crashes when you click on a hyperlink to a Word document.
Word no long displays a spurious "No differences" found dialog when you
compare revisions. (Also job015145)
Word no long displays an error when a document that has been saved with the View>Outline
mode set is compared with the head revision.
Word no longer displays a "String too long error" when comparing revisions.
P4OFC no longer encounters an error condition when you attempt to compare protected documents
P4OFC now handles connections to secure mode servers, and prompts for password as required.
Excel no longer crashes whenever you double-click a .xls file in Windows Explorer.
Word no longer crashes when you click the Perforce menu.
Powerpoint no longer displays a spurious check-in dialog and error when you choose
Print and click Preview...
Perforce->Options" checkbox "Display diff (compare versions) question dialog" now works correctly.
Bugs fixed in 2003.2
Opening .doc by double-clicking the file in Windows Explorer
causes the file to be opened in Read-Only state with disabled
check-in/check-out Perforce menu options.
Excel error when checking in edited non-head revision
Error when printing a Word 97 document using the Windows Explorer
(right-click on name, then choose "print").
Sync to an earlier version using P4Win fails if the file is open
Check-in fails silently if submitting out-of-date file with head
P4OFC requires drive letters to be in uppercase in view mappings
when the user has specified a null root.
Error ("Cannot find startup path") while installing P4OFC with
An error occurs when adding a file in P4OFC if the client root is
a network drive mapped to a drive letter.
Uninstalling P4OFC causes P4Win to quit with errors.
Uninstalling P4OFC does not remove the Perforce menu from Word.
Add release notes.