The publications department where I work has experienced a persistent file deletion bug using Adobe FrameMaker 9 (version 9.0p255) for the past few months. The bug only occurs when opening FrameMaker books from the network share drive in Windows 7. This network share drive appears identical to a local drive. When copying FrameMaker projects to the local hard-drive the problem does not occur. However, it's essential to work off the network share drive so that other writers see FrameMaker locked files and do not work on those files simultaneously.
Steps to reproduce issue follow.
Scenario #1:
Scenario #2:
Scenario #3:
My theory is that a bug in FrameMaker while using operations on multiple files (a common denominator in Scenarios 1-3) is causing the files to get deleted on the network drive. Although the network folder looks identical in Windows 7, each file operation is going over the network instead of directly to files on the local hard-drive.
Is there a network version of FrameMaker? The reason the company doesn't have a network version, if such a version exists, is because each writer has a licensed FrameMaker copy on their local machine. FrameMaker interacts with network folders as if these folders were local folders. However, all operating system file operations are going over the network instead of going to the local drive. The network must therefore emulate the local drive. Is there a network version of FrameMaker that addresses this dynamic, or is the version sold for individual users supposed to operate on both local and network drives? If the latter is the case, then this could be a bug.
Again, we need to work off the network because if multiple writers are working on separate features within a single book, the only method of avoiding collisions between writers is through the FrameMaker file locking feature. By copying files from the network to a local drive, making changes, and then copying the files back to the network, there is a danger of over-writing another writer's work. I can personally get away with copying down files because I'm assigned to an entire book, but that is not always the case.
Has anyone else experienced this issue? If so, please share your workaround.
Thanks,
Eugene
Steps to reproduce issue follow.
Scenario #1:
- Open a FrameMaker book file (where the book and associated FM files are contained in a file folder) on the network share drive.
- Generate a TOC.
Result: Files in book randomly disappear from FrameMaker project folder. After restoring the files and running the TOC again, files randomly vanish again. I use the phrase "randomly vanish" because which files vanish is unpredictable and constantly changing every time the TOC is generated.
Scenario #2:
- Open a FrameMaker book file (where the book and associated FM files are contained in a file folder) on the network share drive.
- Highlight all the files in the book.
- Select View > Hide Conditional Text Indicators.
Result: Similar to Scenario #1.
Scenario #3:
- Open a FrameMaker book file (where the book and associated FM files are contained in a file folder) on the network share drive.
- Highlight all the files in the book.
- Select Format > Document > Change Bars.
- Modify any setting(s) within the Change Bars Properties dialog box.
- Click Set.
Result: Similar to Scenario #1.
My theory is that a bug in FrameMaker while using operations on multiple files (a common denominator in Scenarios 1-3) is causing the files to get deleted on the network drive. Although the network folder looks identical in Windows 7, each file operation is going over the network instead of directly to files on the local hard-drive.
Is there a network version of FrameMaker? The reason the company doesn't have a network version, if such a version exists, is because each writer has a licensed FrameMaker copy on their local machine. FrameMaker interacts with network folders as if these folders were local folders. However, all operating system file operations are going over the network instead of going to the local drive. The network must therefore emulate the local drive. Is there a network version of FrameMaker that addresses this dynamic, or is the version sold for individual users supposed to operate on both local and network drives? If the latter is the case, then this could be a bug.
Again, we need to work off the network because if multiple writers are working on separate features within a single book, the only method of avoiding collisions between writers is through the FrameMaker file locking feature. By copying files from the network to a local drive, making changes, and then copying the files back to the network, there is a danger of over-writing another writer's work. I can personally get away with copying down files because I'm assigned to an entire book, but that is not always the case.
Has anyone else experienced this issue? If so, please share your workaround.
Thanks,
Eugene
______________________
“I do not fear computers
I fear lack of them.” -Isaac Asimov
_______________________________________________
You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to framers@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
