New Features in 2.0c

Workgroup Imaging - Watermark Professional Integration

PC DOCS OPEN 2.0c features Workgroup Imaging.  Integration with Watermark Professional, accomplished via ODMA, allows users to scan images and store and manipulate them under PC DOCS OPEN.  Images can be run against the Watermark OCR tool and the text edited in a word processor.  See the Workgroup Imaging User's and Implementation Guides for further information.

Application Maintenance

Two options have been added to the Integration combo box on the Launch Methods sub-menu.  The first, ODMA Compliant is used exclusively with Watermark Professional.  
The second, Full Integration with Quick Save may be used with any integrated word processing application.  Choosing this option will cause PC DOCS OPEN to save the document on screen more quickly when a File/Save is issued.  This occurs because the Document History is updated and shadow copies are saved only when a File/Close is issued.

Note	If your site uses Cost Recovery, the Full Integration with Quick Save option is not recommended, since the Document History's Edit Time and Keystrokes will not be accurate.

DocuComp 3.0 for Windows

DocuComp for Windows is a program for document comparison and redlining.  DocuComp can be used to compare two versions of a document, or 2 different documents, and mark all deletions, insertions, moved text, and replace text in both versions.  The differences are reported in a "composite file."  In PC DOCS OPEN, the output report may be saved as an attachment or as a version, or may simply be viewed.  
Under PC DOCS, DocuComp for Windows can be run without intervention by the user.  It will compare documents prepared by the same application (for example, WordPerfect 6.0 for Windows) or by different applications (for example, WordPerfect 6.0 for Windows and Ami Pro 3.1 for Windows) automatically.  

Windows Setup

When installing DocuComp for Windows, the user has the option of choosing which word processing applications to attach to DocuComp. For the attach to be complete to the extent DocuComp runs without operation intervention, it is necessary that those applications be known to Windows Program Manager; the applications should be on the Windows Desktop. 

Library Maintenance Setup

In Library Maintenance, all word processing applications need to have DocuComp for Windows listed as a compatible application.  In addition, if it is likely documents from different word processing applications (i.e., WordPerfect, Ami Pro, Word) will be compared, it is necessary those applications have the other(s) listed as a compatible application.  

DocuComp for Windows recognizes the applications from the file extension.  Therefore, in Application Maintenance, it is necessary to choose the Enhanced Filing Scheme for each of the word processing applications.  

Application Maintenance for DocuComp

Application ID:		DCWIN
Description:		DocuComp for Windows
Filing Scheme:		Enhanced
Default Extension:	DUC

Launch Methods (there are three separate launch methods for DocuComp)

Note	Command line parameters [a] and [v] are case sensitive

Launch Method #1
Description:			Save Output as Attachment	
Location:			drive:\path\dcwin.exe 
				(i.e., C:\MASTRSFT\DCWIN.EXE)
Command Line Parameters:	%ATFILE[%FULLPATH %PROMPT 
				[Compare to Document] %OUTPUT [a]]
Default Directory:		drive:\path (i.e., C:\MASTRSFT)
OS Environment:		Windows 3.X
Integration:			No Integration

Launch Method #2

Description:			Save Output as Version
Location:			drive:\path\dcwin.exe (i.e., C:\MASTRSFT\DCWIN.EXE)
Command Line Parameters:	%ATFILE[%FULLPATH %PROMPT 
				[Compare to Document] %OUTPUT [v]]
Default Directory:		drive:\path (i.e., C:\MASTRSFT)
OS Environment:		Windows 3.X
Integration:			No Integration

Launch Method #3

Description:			View Output
Location:			drive:\path\dcwin.exe 
				(i.e., C:\MASTRSFT\DCWIN.EXE)
Command Line Parameters:	%FULLPATH %PROMPT [Compare to Document] 
Default Directory:		drive:\path (i.e., C:\MASTRSFT)
OS Environment:		Windows 3.X
Integration:			No Integration

Note	DocuComp for Windows saves the output file in the file format of the secondary document, but PC DOCS saves the output file as an attachment to the primary document.  This is why the applications must be set up as compatible to one another.  If the primary and secondary documents were created in different word processing applications (WordPerfect 6.0 and Ami Pro 3.1), the user will not be able to access the output file easily.  In this example, the attachment will be in the format of Ami Pro 3.1, but will be attached to the WordPerfect 6.0 document.  The user must launch WordPerfect 6.0  from the PC DOCS OPEN Desktop, choose File/Open and select the Ami Pro 3.1 document, then either click on attachment and select the DUC attachment, or select the version created by DocuComp.  When prompted, the user must click on "import document into current application".  Then the version or attachment will be imported into WordPerfect 6.0.  

New Method for Integrating with Word 6.0

In PC DOCS OPEN version 2.0c, you can put the Word Integration file, (WORDIN60.DOT) into the Word \STARTUP directory.  Optionally, you may also install integration in the original method of opening the file and clicking "Install Macros."  Do NOT, however, both install the macros and put the file in the \STARTUP directory.  Duplicate menu items will be displayed if you do.

If you put the WORDIN60.DOT into the \STARTUP directory, you must copy the AutoNew, AutoClose and AutoExec macros into the NORMAL.DOT. 
Because the AddMacros macro is not being executed, as it is when you install with the original method, the list of recently edited files on the File menu is still displayed.  The AddMacros macro removes these since PC DOCS is not integrated with this feature.  You may turn off this feature manually from within Word.

To setup Word 6.0 integration by using the \STARTUP Directory

1.	If you are upgrading, before you begin, you must remove the integration macros by using Shift/Open to retrieve the old integration file (formerly called WORDIN60.DOC) and click the Remove Macros button.  Click on the Exit button in the file and answer "Yes" when asked to save Global Command and Glossary changes.

2.	Upgrade PC DOCS OPEN.

3.	Copy the WORDIN60.DOT into the Word 6.0 /STARTUP directory.  

4.	Launch Word from the PC DOCS OPEN Desktop. 

5.	Select Tools/Macro.  All active template macros are displayed.  Click on the Organizer button.

6.	The NORMAL.DOT is displayed on both sides.  Click the Close File button under the left display.  It will become Open File.  Click here to display available templates.  

7.	Choose WORDIN60.DOT.  All the macros contained in the integration template will be displayed.  Select AutoClose, AutoExec, and AutoNew one at a time and copy them to the NORMAL.DOT file.

8.	Choose Close, then File/Exit, answering Yes when asked to save global command and glossary changes.

Unintegrating

If you attempt to remove macros by opening the WORDIN60.DOT file and selecting the Remove Macros button the following error message may appear.
	WordBasic Err 100
	Syntax Error
This message indicates simply that the application is integrated by placing the WORDIN60.DOT file in the \STARTUP directory rather than in the original method.  
Click OK through the message and unintegrate in the following manner:

1.	Select Tools/Macro

2.	Select NORMAL.DOT in the Macros Available In field.  Delete each of the three files individually.  

3.	Exit the application saving global command and glossary changes.  

4.	Remove the WORDIN60.DOT from the \STARTUP directory.

Note	If your system has network and local copies of Word 6.0, the individual users' WINWORD6.INI files will indicate which setup Word should look for.  It is possible to select the launch method for the network copy and have your WINWORD6.INI file pointing to the local copy of Word and NORMAL.DOT.  This will not present a problem UNLESS the network has been integrated differently than the local copy.  Suggestion:  Pick one of the methods of integration and use it company-wide.


Minor Enhancements

Print from Quick Retrieve while in an Application

The Print option on the Quick Retrieve Document menu was gray while in applications in previous releases.  This option has now been enabled.

Calculating Pages Printed in WordPerfect 5.2 and 6.0

Previous versions of PC DOCS OPEN had the following problems printing in WordPerfect:  when selecting File/Print from the middle of a document, the cursor would return to the top of the file after printing.  This has been fixed.  Also, the number of pages was not being calculated correctly in the Document History if you changed page numbering in your document, such as i, ii, iii, iv, 1,2,3,4,5.  If you selected Print All using this scenario, the History entry would be 5 instead of 9.  New DDE settings for WordPerfect 5.2 and 6.0 have been added that will correct this problem when you print from within the application.  Please type these new DDE settings in your WordPerfect definitions in Application Maintenance, Launch Methods, DDE Settings.

The new DDE Settings are:

WordPerfect 5.2 

Command.  UserFunction(" PCDOCS:Print:%1")
Command not running.  UserFunction("PCDOCS:Print:%1")AppClose()

WordPerfect 6.0

Command.  UserFunction("PCDOCS:Print:%1")
Command not running.  UserFunction("PCDOCS:Print:%1")ExitWordPerfect()

Pages printed will be calculated if you have PAGEPRINTEDWP52 in the PCDOCS.INI file under [Application Integration], indicating that you wish to calculate pages printed.  Pages printed are not, however, calculated if you print from the PC DOCS OPEN Desktop.  A print history will be noted, but the page count will be 0.

Saving WordPerfect 6.0 Document Summary 

In version 2.0c, you may save WordPerfect 6.0 Document Summary information as a new document under PC DOCS OPEN.  This is done by selecting File/Document Summary, then choosing Save as a New Document.

Quicker Profile Field Lookups

In version 2.0c, when filling out a profile field, you may type a partial value, then press Tab.  PC DOCS will attempt to find a match.  If a unique value is found, the field will be populated with that value.  If several values are found, a table lookup displaying those values will be displayed.

Also, you may perform a table lookup on the Matter field (or similar child fields) when the Client (or parent) field is blank.  Choosing an entry will populate both the parent and child fields.

Streamlined Launch Methods

In version 2.0c, when an application is selected from the Desktop, the only Launch Methods displayed are those applicable to the current user.  If the list only shows one method, the form is not displayed.

Release Code Date on Help Menu Option

The Help menu option "About PC DOCS" now shows the release code date for the integration file being used.

DOCSOPEN for DOS

Quick Retrieve

Quick Retrieve in DOCSOPEN for DOS has been enhanced to function more like the Windows Client.  The field Open Document has been added, and functionality is similar to that in the Windows Client.

You may now open a document from the Quick Retrieve by entering either the Document Number or Document Name in the Open Document field.  If you enter a Document Number, PC DOCS will open the document.  If you enter the Document Name, and the name is unique, the document will be opened.  If the Document Name is non-unique, a listing of documents sharing that name will be returned.

Format for the Open Document field is as follows:

libraryname\doc#|docname

The library name, if needed, must be followed by a back-slash(\).  The document is indicated by name or by number.  If the document is in your primary library, the library name is unnecessary.  If a library name is used it must be defined as a remote library of your primary library.

Auto-Delete of Shadowed Documents

If enabled, this feature automatically removes shadowed documents from the local drive. Documents that are older than the Minimum Age For Delete are deleted each time you exit the DOCSOPEN for DOS.  This feature is enabled by indicating "Yes" in the System Parameters, Shadowing field Auto-Delete Shadowed Documents.  The Minimum Age For Delete (Days) is also determined here.

Issues Fixed in 2.0c

Applications

Integration

Issue Number:  6719 New Feature
In previous versions, the Quick Retrieve Document/Print option was grayed while in an application.  This option is now enabled.

Issue Number:  6115
The Word footer macro has been added to WORDIN60.DOC and WORDIN20.DOC (the integration setup files for Word 6.0 and 2.0).  There is no longer a need for a separate setup of this macro.

Issue Number:  6005
In previous versions, after the Word integration file was run (WORDIN60.DOC or WORDIN20.DOC) the Windows clipboard was not being cleared and a corresponding message was being displayed when Word was closed.  The clipboard is now cleared.
Word 2.0

Issue Number:  6323
In previous versions of PC DOCS OPEN, if you installed Word 2.0 integration twice in a row without uninstalling, extra menu options were displayed.  This has been fixed.

Issue Number:  6272
In previous versions, the Summary Info "User" was incorrectly being pulled from Word rather than the Profile Author. This has been fixed.

Issue Number:  6234
In previous versions, if you issued a File/Close in Outline View a MS Macro error 509 was generated.  This has been fixed.

Issue Number:  6218
In previous versions, if you opened a WordPerfect document or text file in Word, made no edits, then closed, you were prompted to save anyway.  Now, you will not be asked to save changes.

Word 6.0

Issue Number:  6711
In previous versions, form fields were cleared when saving the document.  This has been fixed

Issue Number:  6710, 6707
Previous versions of PC DOCS OPEN caused template documents to be opened as read-only.  This has been fixed.

Issue Number:  6706
In previous versions, if you had a Word 6.0 protected document that was designated as a template document on the PC DOCS OPEN profile, when you tried to open the document from Quick Retrieve inside of Word it would open the template as a read only document and not let you save changes. If you opened the document from Quick Retrieve without Word 6.0 running, it opened the document, and let you profile it, but a Word Basic Error 509 message was issued stating that you cannot protect the document because it is already protected.  This has been fixed.  You must unprotect and then reprotect the document with the new integration before file created before PC DOCS OPEN will work properly.

Issue Number:  6601
In previous versions, the password was not being saved to the shadow copy on the local drive when a protection password only was used.  If both a protection and write protect password were used, both were saved properly.  This has been fixed.

Issue Number:  6319
Prior to 2.0c, when opening a "being edited" file as read only, a message indicating that the file is in use was coming from the application.  This has been fixed.

Issue Number:  6273
In previous versions, the Summary Info was pulling the user information from Word rather than from the Profile Author.

Issue Number:  5935, 6581  New Feature
In PC DOCS OPEN version 2.0c, you can put the Word Integration file, (WORDIN60.DOT) into the Word \STARTUP directory.  Optionally, you may also install integration in the original method of opening the file and clicking "Install Macros."  Do NOT, however, both install the macros and put the file in the \STARTUP directory.  Duplicate menu items will be displayed if you do.
If you do put the WORDIN60.DOT into the \STARTUP directory, you must copy the AutoNew, AutoClose and AutoExec macros into the NORMAL.DOT.

WordPerfect 5.2

Issue Number:  6609
In previous versions, after disabling integration, when performing a Tools/Merge/Merge, PC DOCS OPEN messages were still being displayed.  This has been fixed.

Issue Number:  6386
In previous versions, when you tried to print a document with WordPerfect 5.2 and made Graphics print changes on the print form, application errors were being issued.  This has been fixed.

Issue Number:  5340 New Feature
Previous versions of PC DOCS OPEN had the following problems printing in WordPerfect:  when selecting File/Print from the middle of a document, the cursor would return to the top of the file after printing.  This has been fixed.  Also, the number of pages was not being calculated correctly in the Document History if you changed page numbering in your document, such as i, ii, iii, iv, 1,2,3,4,5.  If you selected Print All using this scenario, the History entry would be 5 instead of 9.  New DDE settings for WordPerfect 5.2 and 6.0 have been added that will correct this problem when you print from within the application.  
The new DDE Settings are:
	WordPerfect 5.2 
Command.  UserFunction(" PCDOCS:Print:%1")
Command not running.  UserFunction("PCDOCS:Print:%1")AppClose()
	WordPerfect 6.0
Command.  UserFunction("PCDOCS:Print:%1")
Command not running.  UserFunction("PCDOCS:Print:%1")ExitWordPerfect()

Pages printed will be calculated if you have PAGEPRINTEDWP52 in the PCDOCS.INI file under [Application Integration], indicating that you wish to calculate pages printed.  Pages printed are not, however, calculated if you print from the PC DOCS OPEN Desktop. A print history will be noted, but the page count will be 0.

Issue Number:  3123
In version 2.0c, the macro enabling integration with PC DOCS OPEN is run each time WordPerfect is exited.  This is to prevent users from disabling integration for a file import, then forgetting to reenable later.

WordPerfect 6.0

Issue Number:  6730
In PC DOCS OPEN 2.0c, the WordPerfect 6.0a Document Comparison feature performs comparison by word, sentence, or paragraph.

Issue Number:  6667 New Feature
Previous versions of PC DOCS OPEN had the following problems printing in WordPerfect:  when selecting File/Print from the middle of a document, the cursor would return to the top of the file after printing.  This has been fixed.  Also, the number of pages was not being calculated correctly in the Document History if you changed page numbering in your document, such as i, ii, iii, iv, 1,2,3,4,5.  If you selected Print All using this scenario, the History entry would be 5 instead of 9.  New DDE settings for WordPerfect 5.2 and 6.0 have been added that will correct this problem when you print from within the application.  
The new DDE Settings are:
	WordPerfect 5.2 
Command.  UserFunction(" PCDOCS:Print:%1")
Command not running.  UserFunction("PCDOCS:Print:%1")AppClose()
	WordPerfect 6.0
Command.  UserFunction("PCDOCS:Print:%1")
Command not running.  UserFunction("PCDOCS:Print:%1")ExitWordPerfect()

Pages printed will be calculated if you have PAGEPRINTEDWP52 in the PCDOCS.INI file under [Application Integration], indicating that you wish to calculate pages printed.  Pages printed are not, however, calculated if you print from the PC DOCS OPEN Desktop. A print history will be noted, but the page count will be 0.

Issue Number:  6529
In previous versions, if you chose File/Exit in WordPerfect 6.0 with a modified document on screen, then chose "Cancel" when PC DOCS OPEN asked you if you wished to save changes, you would then be prompted with a WordPerfect message asking if you wished to save changes. The second message should not have been displayed.  This has been fixed.

Issue Number:  6457
The ALT F4 hot key to exit WordPerfect is now integrated.

Issue Number:  6456
The Exit and Close No Save buttons on the WordPerfect 6.0 button bar are now integrated.

Issue Number:  6358
In previous versions, if you used the disable macro to unintegrate with PC DOCS, when File/Exit was selected with an edited document on the screen, a PC DOCS OPEN prompt was being displayed.  This has been fixed.

Issue Number:  5730
In previous versions, if you were using WordPerfect 6.0 and PC DOCS OPEN in normal window size, then toggled to the Program Manager and closed the windows, multiple General Protection Faults were issued.  This has been fixed.

Issue Number:  3514 New Feature
In version 2.0c, you may save WordPerfect 6.0 Document Summary information as a new document under PC DOCS OPEN.  This is done by selecting File/Document Summary, then choosing Save as a New Document.

Excel 5.0

Issue Number:  6703
In previous versions, when a document is opened as read-only when File/Save As was chosen, a message rather than a new profile was displayed.  A profile is now displayed.

Issue Number:  6638
In previous versions of PC DOCS OPEN, when printing using the icon on the Excel toolbar the entire workbook is printed, rather than the current worksheet, as in native Excel.  This has been fixed.

Issue Number:  6527
In previous versions, when using the /E Command Line Parameter in Application Maintenance Launch Methods a PC DOCS message box stating OBJECT VARIABLE NOT SET is displayed during launch.  This has been fixed.

Issue Number:  6514
In previous versions of PC DOCS OPEN, if you launched Excel, chose File/Open, then selected a template document from the Quick Retrieve, then chose Use Template, a blank screen, rather than the template would be displayed.  This has been fixed.

Issue Number:  6295
In previous versions, when using Auto Close to close an Excel 4.0 Workbook in Excel 5.0, PC DOCS OPEN would issue a message that the Excel 4.0 integration file (DOCSXL40.XLA) could not be found.  This has been fixed.

Quattro Pro 5.0

Issue Number:  6217
In previous versions, when performing a multiple document open from the Quick Retrieve, the PC DOCS OPEN Select Launch Methods screen for the second document's application was being hidden by the first opened document.  This has been fixed.  The Select Launch Method form will always be the top window now.

Issue Number:  5337
The Quattro Pro speedbar was not integrated with PC DOCS OPEN.
To set up your Quattro Pro 5.0 speedbar with PC DOCS OPEN functionality, perform the following steps:

1.	Create a new speedbar, adding the necessary buttons (either create your own bitmaps or simply use words).

2.	Select Links, then Add.

3.	Click Receive, then select DOMACRO. 

4.	In the space provided, enter the appropriate PC DOCS macro call.  The macros available are:  _FileSave, _FileOpen, _FileClose, _FileSaveAs, _FileRetrieve, _FileCloseAll, _FileExit, _Insert (for Block/Insert/File), _FileNew, _ToolsExtract, _ToolsCombine, _WorkSave (File/Workspace/Save), _WorkRestore, _GraphicImport, _FilePrint.  The correct syntax when executing a macro is {_FileOpen}.  So, when you enter you macro be sure to include the {}.

Lotus 123

Issue Number:  6432
In previous versions of PC DOCS OPEN, if you had a spreadsheet open in Lotus 1-2-3, then selected File/Open/Combine, then picked a file from the Quick Retrieve, then selected CANCEL from the Combine dialog box, the file would be locked, and could not be opened until Lotus or PC DOCS was exited.

Issue Number:  6182
In PC DOCS OPEN 2.0c, you may create several documents using File/New, without being asked to save them before the next is created.  The temporary filenames file1, file2, etc. are given until the documents are saved and properly named.

Issue Number:  5268
Accelerator Yes and No buttons were added to all Lotus 1-2-3 dialog boxes.

Ami Pro 3.0/3.1

Issue Number:  6455, 5986
In previous versions, PC DOCS OPEN would not let you cancel out of Save as with Password.  If you tried, you would receive the message "Unable to save the network copy" and were forced to enter a password.  Now when you cancel out of the password dialog box, the file will be saved without a password.  This was also an issue with Ami Pro 3.02.

Issue Number:  6277, 6374
Prior to 2.0c, when specifying pages to be printed, if you used the arrow keys to select a number, and scrolled past 9999, you would go to 1000 (rather than back to 1).  The up arrow would then become disabled.  This has been fixed. This was also an issue with Ami Pro 3.02.

Issue Number:  6128  New Feature
The Help menu option "About PC DOCS" now shows the release code date for the integration file being used.

Issue Number:  5745
In previous versions, when merging, and choosing "other file types" for the description file,  an error was produced.  This has been fixed.

Issue Number:  5736
In version 2.0c, several menu items are being grayed during activity to prevent the user from causing errors to occur.

Database Import

Issue Number:  6642
In previous versions, the Database Import Utility could not properly import files with underscores in the filenames.  This has been fixed.

Designer

Issue Number:  6460
In version 2.0c, a double click is required to expand/contract a branch in the SQL columns listing.  The + and - keys will also expand and contract now.  This corrects problems associated with adding fields.

Issue Number:  5529  New Feature
In version 2.0c, when filling out a profile field, you may type a partial value, then press Tab.  PC DOCS will attempt to find a match.  If a unique value is found, the field will be populated with that value.  If several values are found, a table lookup displaying those values will be displayed.

Issue Number:  5520  New Feature
In PC DOCS OPEN version 2.0c, you may perform a table lookup on the Matter field (or similar child fields) when the Client (or parent) field is blank.  Choosing an entry will populate both the parent and child fields.

Issue Number:  5515
In version 2.0c, if you clear out the Client field (or any parent field), the Matter (child) field is also cleared.  This prevents the user from selecting a Client, then a Matter, then changing the Client, thereby setting up an invalid relationship.  A secondary validation was applied.

Desktop

Issue Number:  5811
In version 2.0c, the local \WINDOWS directory, then the network \DOCSOPEN\PROGS directory will be checked for the PCDOCS.INI file.  All aspects of the PCDOCS.INI file will be read from the local copy (if one exists) rather than the network copy.  This will allow individuality among users in a variety of areas.  The Chapter 1 in the PC DOCS OPEN Supervisor's Guide discusses the PCDOCS.INI file indepth.

Issue Number:  6660   New Feature
In version 2.0c, when an application is selected from the Desktop, the only Launch Methods displayed are those applicable to the current user.  If the list only shows one method, the form is not displayed.

Issue Number:  6405
The Check-in document form Check-in Time field now accepts times only within the range of  0 to 1440 minutes.

Issue Number:  6253
In previous versions, if you used the File/Import File feature, then filled out the profile and chose OK, then clicked OK a second time, a General Protection Fault would be issued.  This has been fixed.

Issue Number:  6228
In previous versions, if you tried to copy a document (Document/Copy) whose profile had more than 16 table lookups, an SQL error would be given.  This has been fixed.

Issue Number:  6221
In previous versions, after performing a Document Import, United Kingdom date formats were reversed.  If you performed a profile search on imported documents and viewed the Search Results form containing the Creation Date column in the list box the date would be displayed in reverse.  For example, if in File Information the date of the file is 01/03/94 it will be displayed on the Search Results form as 03/01/94.  This has been fixed.  The date format will be based on the WIN.INI date setting.

Issue Number:  6210
In previous versions, if you had a Quick Retrieve screen with no documents in the Recently Edited Documents listing (for example, in a database you have never used before) and you entered a valid Document Number in the Open Document field, the document would not be found.  Also, after doing a profile search on just that document number, upon returning to Quick Retrieve the document was not highlighted in the list, and the document could not be opened.  This has been fixed.

Issue Number:  6198
In previous versions, if you were using Auto-Delete of Shadowed documents at PC DOCS startup, PC DOCS would pre-connects to all remote libraries for the server.  If you were not a valid user on all libraries you would be notified with a warning message.  Now, if the connect to the library fails because the user doesn't exist, no error/warning will be displayed, PC DOCS will simply skip that library and continue.

Issue Number:  6171
In version 2.0c, when you perform a Profile Search, the found document will be highlighted so that pressing ENTER will retrieve the document.  If several documents are found, the first document is highlighted.

Issue Number:  6164
In previous versions, if no document was highlighted in the Quick Retrieve document listing, PC DOCS OPEN would ignore any entry in the Open Document field.  This has been fixed.

Issue Number:  5945
In previous versions, if Quick Retrieve were pulled up from inside an application (by performing a File/Open, etc.) the PC DOCS OPEN Help menu was not functional.  This has been fixed.

Issue Number:  5706
In PC DOCS OPEN 2.0c, you may print documents from the Quick Retrieve Document menu while within an application.

Issue Number:  5658
In previous versions, the Directory Monitor was not properly monitoring subdirectories for documents created outside of PC DOCS OPEN, even with the "Include Sub-directories" box checked in Application Maintenance.  This has been fixed.

Issue Number:  5553
In previous versions, the Group Maintenance Utilities form allowed the hot key ALT-O for the "Run Document Import" field.  This has been changed since the OK button uses ALT-O

Issue Number:  5507
In previous versions, if a user hit the Enter key twice on the profile search screen, PC DOCS OPEN would return the entire profile database.  The second enter was actually an "OK" to a message box stating: "Warning - this search will return all profiles".  Now, Cancel is the default button on this message box, so pressing enter twice would Cancel the search rather than perform it.

Issue Number:  5505
In previous versions, extraneous spaces at the end of search criteria were being considered valid and searches were returning no results.  Now blank spaces at the end of fields is ignored in searches.

Issue Number:  5500
In previous versions, all users had access to the Full Text Indexer from the Options/System Utilities menu.  Now, this option is displayed only if the user belongs to DOCS_SUPERVISORS.

Issue Number:  5437
In previous versions, if you changed a document profile's Document Type from a keep type to a delete type, the Storage type and Retention Days would be changed appropriately, but the process date was set to the current date instead of adding Retention Days to the Last Edit Date.  This has been fixed.

Issue Number:  5134
In version 2.0b, when you created a document by copying it from another document, the edit date for the new document defaulted to the edit date of the original document.  This made the History's Total Time for the document wrong.  This has been fixed.

Issue Number:  5121
In version 2.0b, if you performed a search from Quick Retrieve, then edited the profile of a document in the document listing, when you clicked OK to save the profile changes, a General Protection fault was given.  This has been fixed.

Issue Number:  5083
In previous versions, if monitoring a directory for documents created outside PC DOCS OPEN on any drive other than f: or c:, users would not be prompted to profile their documents.  This has been fixed.

Issue Number:  4501
In previous versions, if a user selected Document/New Document, and no templates were defined, an error message was displayed, then the blank template list was displayed anyway.  Now, the template list is not displayed if no templates exist.

Issue Number:  3414
In previous versions, if document profiles were edited, changes were not reflected on Quick Retrieve screens or Hit Lists that were already open before the edit was performed.  This has been fixed.

Issue Number:  2542
In previous versions, a Save was the only action that would reset the Last Accessed Date of a document.  This date is what determines when a document is archived or deleted.  Now copy, read, and retrieve update the Last Edit Date.

Issue Number:  2219
In previous versions, if the Full Text Indexer had not been run, and a user performed a Full Text search, a General Protection Fault was issued.  This has been fixed.

Issue Number:	6875
In version 2.0c, if you have a document open, and attempt to use Quick Retrieve to print the document, rather than the application's own print function, a message will be displayed reminding you that the document is open and that you should print with the application's print command.

Issue Number:	6815
In previous versions, if you performed a Profile Search accidentally entered spaces in an otherwise blank field, you would get no hits.  Now, white space is removed from Profile fields before the search is performed.

Issue Number:	6615
In previous versions, if a launch method exists that references a drive that some users do not have (such as D:),  the user who does not have the drive received an error message when they loaded PC DOCS OPEN.  This has been fixed.

Issue Number:	6071
In previous versions, if you saved a document, filled out the profile, clicked OK, then made a change to the profile before clicking Close, a General File Protection error would be given.  Now, clicking OK will close the profile.

Document Import

Issue Number:  6532
The Document Import utility now gets Table ownership information from the FCREATOR column in DOCSCOLUMN rather than hard coded "docsadm".

Issue Number:  5660
In previous versions, when using LanMan and importing documents, errors were produces when DOCS_USERS did not have create rights.  This has been fixed.

Issue Number:	6841
In previous versions, if you imported a set with no document or version location specified, you would receive a General File Protection error.   Now you will be notified that you need to provide the information rather than receiving an error.

Full Text Indexer

Issue Number:  6200
In previous versions the Full Text Indexer ellipses for Index Location (in the Full Text Indexer setup) did not translate the drive letter to server/volume name.  This is necessary, because the drive letter is not always the same for every user.  The server/volume name is now translated.

Library Maintenance

Issue Number:  6709
In previous versions, problems existed in synchronizing users when Lan Manager and Windows for Workgroups were being used together.  If the server is using Lan Manager, but the workstations are only using Windows for Workgroups drivers, Windows would report that Windows for Workgroups was the network type and only those users logged in at the moment of synchronization would be synchronized.
To correct this problem, a new PCDOCS.INI setting has been added, allowing you to specify the network type, causing PC DOCS to ignore what Windows says the network type is.  In PCDOCS.INI add:

[Network]  
Override=512    

This number tells PC DOCS the network is type Lan Manager.  This enhancement was created to fix the stated problem, and should not be used in other cases.

Mobile

Issue Number:  6743
PC DOCS Mobile has problems if the 32 bit access file access is used.  The -d command parameter for Watcom prevents this from happening.

Issue Number:  6676
In previous versions, under certain circumstances, the Mobile document path was placing the first character of the first directory as a new directory from the root.  For example, if the directory should have been \DOCS\B_BAILY it became \D\DOCS\B_BAILY.  This has been fixed.

Issue Number:  6666
Previous versions of PC DOCS Mobile had problems downloading validation data, subsequently causing problems with document check out.  This has been fixed.
Storage Management

Issue Number:  6478
In previous versions, the Storage Management utility couldn't handle document moves between libraries if the filing scheme (standard or enhanced) did not match on both libraries for a given application.  The documents were moved; however, they were copied to the new library template path in the original filing scheme.  Errors were given when users tried to open the documents.  This has been fixed.

Issue Number:  6336
The Storage Management Utility gave invalid errors when the number of legitimate errors equaled the number specified in the FILE= command in the CONFIG.SYS.  Now, open file handles are closed before returning the error condition.

Issue Number:  6098
In previous versions, if you changed the retention days on the profile for a document with Storage=A(rchive) the process date was incorrectly calculated to be today+previous retention days value instead of revised retention days.  This has been fixed.

Issue Number:  5476
In previous versions, if the server or volume names contained underscores (_), the Storage Management utility could not properly read the names.  This has been fixed.

Issue Number:	6318
In previous versions, if you were using Netware 4.0, and tried to save a document to a server other than your primary server, you would be prompted to login to the other server.  With Netware 4.0, you should not be prompted to login, it should be done for you automatically.  This has been fixed.

Issue Number:	6261
In previous versions, when moving documents to optical, trustees were not properly being applied.  This has been fixed.

ADDUSER

Issue Number:	6762
In previous versions, the ADDUSER.EXE program was not working properly.  This has been fixed.

TBLCOMP

Issue Number:	6852
In previous versions, the TBLCOMP.EXE program inserted DOS_USERS as a PC DOCS OPEN group. This column is now inserted by the DOS Client install.

Issue Number:	6829

In previous versions, the short-cut key for Connect via NetBIOS (ALT-B) did not work.  This has been fixed.

Issue Number:	6827
In previous versions, there were two ALT-O short cut key assignments on the Oracle Connection window:  OK button and Connect via Other. Now OK is ALT-O and Connect via Other is ALT-H.

Issue Number:	6826
In previous versions the Oracle Server field was not required. Now the field is required.

Issue Number:	6822
In previous versions, if there were no PCDOCS.INI  in the \DOCSOPEN\PROGS directory, nor in the local \WINDOWS directory (such as in the case of a new install) if you clicked OK without providing all SQL Vendor information, TBLCOMP.EXE would simply abort.  Now, if all information is not given, default settings will be used.



Documentation Errata

Supervisor's Guide

Page 8-7, the section Disk Space Errors, indicates that shadowed documents may be redirected to an alternate drive by entering

[SHADOWING]
Shadow=D

This should read:

[SHADOWING]
Drive=Driveletter

Clarification for Deletion of Shadowed Documents:  PC DOCS OPEN looks at the first variable in the Shadow Path Template and deletes all files and directories from that level down.  Creating directories in the shadow directory structure is not recommended for this reason.

Chapter 2, Library Maintenance, the Application Maintenance section lists two fields that are incorrectly defined.  The following are correct definitions:

Extensions to Index.  This field is for a feature not yet implemented.  The intention of this option is to allow the indexing of attachments with other extensions.  PC DOCS OPEN cannot index attachments at this time.

File Types.  Originally designed to go along with Extensions to Index, this feature is now being used in the following manner:

List in this field all File Types that you may want imported into the selected application.  For example, enter the DOC extension to the WordPerfect 6.0 application definition.  When you go to the PC DOCS OPEN Desktop and select File/Import File, the profile provided has a combo box associated with the Application ID field listing Word 6.0, Word 2.0 and WordPerfect 6.0.  Without the File Types entry the Word applications would not have been displayed.

WordPerfect 5.2 and 6.0 have new DDE Print settings.  Please type these in your Application Maintenance definitions.

WordPerfect 5.2 

Command.  UserFunction(" PCDOCS:Print:%1")
Command not running.  UserFunction("PCDOCS:Print:%1")AppClose()

WordPerfect 6.0

Command.  UserFunction("PCDOCS:Print:%1")
Command not running.  UserFunction("PCDOCS:Print:%1")ExitWordPerfect()

Appendix A - The Data Dictionary - The PROFILE table lists a column called DOCSERVER.  There is no such column in the PROFILE table.

Chapter 2, Library Maintenance, the variable %library_name may be used in both the Document Path Template and the Shadow Path Template.

User's Guide

Clarification on Full Text Indexing Numbers.  A number must start and end with a digit.  For example, -123 isn't a number, but the 123 part will be captured as a word.  Within a number, the characters dash (-), period (.), comma (,), slash (/), and colon (:) may exist.  Any number of any or all of these are allowed.

If the indexer encounters a character string than begins with a number, but encounters an alpha character (including the allowed foreign characters) then the string is classified as a word (i.e., 123a456 would be parsed as a word).

When performing Profile Searches, if you use the * wildcard as the first character in a Profile Field, such as Document Name, and no other criteria, server utilization could exponentiate.  It is suggested that you use other criteria as well.  You may, however, successfully use the * wildcard and ? wild character as the first character in a full text search.

DOCSOPEN for DOS User's Guide

You may successfully use the * wildcard and ? wild character as the first character in a full text search.

The manual states that when a view document is performed after a Full Text Search, that the search words are highlighted.  This description follows with keys that may be used to maneuver through the document.  This information is specific to the Windows Client and does not apply to DOCSOPEN for DOS.

Designer Guide

When adding Object Items to a radio group, as is described on page 5-6, you must enter Ctrl-Enter on a final line.

Mobile User's Guide

Mobile install files must be placed in the \DOCSOPEN\PROGS directory for proper operation.

Sybase NLM Implementation Guide

On page 3-4, the section Step One, Update NetWare Operating System NLMs, a bullet should be added to the list.  You will be asked to provide a serial number.  If you purchased Sybase from PC DOCS, INC., your serial number is 425087.

Page 3-6, at the bottom of the page, the sample commands describing alteration of the size of the tempdb database is incorrect.

First, diskinit should be all caps:  DISKINIT.

Second, the line	1>alter database tempdb on master=10
should read	1>alter database tempdb on temp=10

On page 4-5, under the Database Device section, please note the following errors:
Line 1 reads	1>DISK INIT NAME='DOCS',
It should read	1>DISKINIT NAME='DOCS',
Line three reads	3> VDEVNO=1 SIZE=7680
It should read	3> VDEVNO=1, SIZE=7680

Application Information

This section includes several items concerning functionality of the different integrated applications.  You should find them useful in using the application with PC DOCS OPEN.

Ami Pro 3.0/3.01

Password protected files should not be launched from the PC DOCS OPEN Desktop.  The DDE settings provided for Ami Pro cannot trap the pause necessary to key in the password, so the launch fails.  Use File/Open from inside the application for password protected files.

If you have multiple Launch Methods for Ami Pro, you should complete the Search path field in Application Maintenance, Launch Methods.  This will enable PC DOCS OPEN to find the correct AUTOEXEC.SMM.

Word 2.0

Word 2.0 and Word 6.0 both run off of the executable WINWORD.EXE.  Microsoft has designed it so that a user cannot open both Word 2.0 and Word 6.0 at the same time.  If you have Word 6.0 launched and on screen and select a Word 2.0 document from Quick Retrieve, PC DOCS processes DDE settings to launch Word 2.0, then sees Word 6.0 already running.  PC DOCS then opens the file in Word 6.0 without any indication that 2.0 is not the application presented.  This confuses PC DOCS and a File/Close causes PC DOCS to not properly release the file.  

The following setup eliminates this problem:

1.	In Library Maintenance set Word 6.0 as a compatible application of Word 2.0 and Word 2.0 as a Compatible application of Word 6.0.

2.	When a file is selected from Quick Retrieve and the profile Application ID does not match the application PC DOCS believes to be running, a dialog message appears with the following options:

		Start this document's application OR
		Import into current application

3.	Choose Import into current application.  If you choose File/Save, the document will be saved in the open application format and the profile will be updated for the new application.  The original will be overwritten in the new application format.  If you choose File/Save As, and choose New Document, you will be asked to profile the new document, with the open application, and the original will be left intact.

Do not select "Start this document's application" since PC DOCS OPEN cannot process this information and file locks will occur.  

Not setting up the applications as compatible will also produce file locks.

Before you begin creating or importing documents in PC DOCS OPEN, to take advantage of mail linking capabilities, you should change Word for Windows 2.0's Filing Scheme in Application Maintenance to Enhanced, rather than Standard.

Word 6.0

You should not Full Text Index Word 6.0 password protected documents.  If you do, errors will occur.

Word 2.0 and Word 6.0 both run off of the executable WINWORD.EXE.  Microsoft has designed it so that a user cannot open both Word 2.0 and Word 6.0 at the same time.  If you have Word 6.0 launched and on screen and select a Word 2.0 document from Quick Retrieve, PC DOCS processes DDE settings to launch Word 2.0, then sees Word 6.0 already running.  PC DOCS then opens the file in Word 6.0 without any indication that 2.0 is not the application presented.  This confuses PC DOCS and a File/Close causes PC DOCS to not properly release the file.  

The following setup eliminates this problem:

1.	In Library Maintenance set Word 6.0 as a compatible application of Word 2.0 and Word 2.0 as a Compatible application of Word 6.0.

2.	When a file is selected from Quick Retrieve and the profile Application ID does not match the application PC DOCS believes to be running, a dialog message appears with the following options:
		Start this document's application OR
		Import into current application

3.	Choose Import into current application.  If you choose File/Save, the document will be saved in the open application format and the profile will be updated for the new application.  The original will be overwritten in the new application format.  If you choose File/Save As, and choose New Document, you will be asked to profile the new document, with the open application, and the original will be left intact.

Do not select "Start this document's application" since PC DOCS OPEN cannot process this information and file locks will occur.  

Not setting up the applications as compatible will also produce file locks.

Before you begin creating or importing documents in PC DOCS OPEN, to take advantage of mail linking capabilities, you should change Word for Windows 6.0's Filing Scheme in Application Maintenance to Enhanced, rather than Standard.
Merging documents in Word 6.0 using PC DOCS OPEN

To create a new merge file:

1.	Create your main document.  This document is automatically profiled when you save.  Use your Word 6.0 documentation for information on creating main documents and data files.

2.	Create your data file.  

3.	After you have completed the field selection for this data file, you will be presented with a native Word Save As dialog.  Give the file a name.  This name is only temporary, since after the data file is profiled, the name will be obsolete.  You may want to use the same name every time.

4.	After naming the file in the native dialog your are returned to the "Merge Helper" which allows you to add records to this file you have just created.  On this dialog is a button "View Source".  Select this button to have the data file displayed in table format.  

5.	Select File/Save and profile the document.  The association of the data file with its profiled name and path are saved into the main document.  

6.	Because you have just created the two files you can use the "Merge Helper" to merge the main file and data files to screen or directly to the printer.  If you choose to merge to the screen, you can profile the merged document for future use.

7.	Later if you wish to associate a new form letter with an old data file, you can use the PC DOCS OPEN merge item to merge the two unassociated files together.  
Note	When editing the data file, the user MUST open the data file from the Quick Retrieve.  Word allows you to toggle to the data file from within the main document.  This opens the data file without PC DOCS, so  when you close, PC DOCS will attempt to profile the document.  Once the file has been opened from Quick Retrieve you can use the toggle button to jump between the main file and data file if you choose.

	When importing a protected document, the user must unprotect, then reprotect the document, then save and profile it.  If you edit the protected document before saving it, your edits will be removed when you save.  This does not happen if you are using a profiled template or have otherwise saved the document in PC DOCS.  It only occurs when edits are made to an imported document before the save.

Excel 5.0

If Excel 4.0 and Excel 5.0 are Compatible Applications, and you attempt to open an Excel 4.0 workbook (with internal links) while in Excel 5.0, choosing to open in the current application (Excel 5.0) you will be prompted to update the links.  You should choose "No."  Because they are  internal links they will remain intact.  A "Yes" causes Excel  to error since it cannot find file docsxl40.xla.  After you choose File/Save and the Excel 5.0 information is saved to the file, future references to updating links will function appropriately.

WordPerfect 5.2

WordPerfect 5.2 has new DDE Print settings.  Please type these in your Application Maintenance definitions.

Command.  UserFunction(" PCDOCS:Print:%1")
Command not running.  UserFunction("PCDOCS:Print:%1")AppClose()

Before you begin creating or importing documents in PC DOCS OPEN, to take advantage of mail linking capabilities, you should change WordPerfect 5.2's Filing Scheme in Application Maintenance to Enhanced, rather than Standard.

You should save all graphics files before issuing a File/Close.

If you use the WP 5.1 DOS keyboard functions Shift-F4 (Open) will cause a native File/Open to be called rather than Quick Retrieve.

WordPerfect 6.0

WordPerfect 6.0 has new DDE Print settings.  Please type these in your Application Maintenance definitions.

Command.  UserFunction("PCDOCS:Print:%1")
Command not running.  UserFunction("PCDOCS:Print:%1")ExitWordPerfect()

Before you begin creating or importing documents in PC DOCS OPEN, to take advantage of mail linking capabilities, you should change WordPerfect 6.0's Filing Scheme in Application Maintenance to Enhanced, rather than Standard.

Printing multiple documents from the Desktop has unpredictable results.  You should print one document at a time from the Desktop.

WordPerfect 6.0aPM (Slipstream) has not been fully tested and therefore is not certified with PC DOCS version 2.0c.  

Quattro Pro 5.0

The ALT F4 hot key used to exit Quattro Pro is not integrated.
The CTRL F4 hot key used to close a document is not integrated.

Because of limitations of the Quattro Pro 5.0 macro language, you may experience intermittent failures of integration with PC DOCS OPEN.  We will be working on this problem and plan to release a tighter version of integration at the earliest possible time.

Lotus 1-2-3

When printing a document, you must enter the range of pages to be printed rather than accepting the default of 1 to 9999.  Accepting the default causes a History entry of 9999 pages printed. 

Printing from the Desktop is not currently functioning.  Printing must be accomplished from within Lotus

The Lotus Autosave will not properly save an unprofiled document.  When an unprofiled document is in focus, the Autosave will try to save it and Lotus presents a native save as screen.  You will need to cancel and select File/Save to profile the document.  The Autosave will work properly from then on.

To maintain a password on a Lotus file, the file must be saved using Save as with Password each time it is saved.  

MS Mail

7174 - Mailing Multiple Secured Documents.  When multiple secured documents are selected to be mailed, the following problem occurs. This is consistent across MS MAIL, Lotus Notes, and Groupwise.

Unless you answers YES to the security warning message for at least one of the documents preceding the last, you will never get the message for the last document.  It is necessary for you to answer Yes to the last document for the documents to be mailed.

Lotus Notes

Mailing Multiple Secured Documents.  When multiple secured documents are selected to be mailed, the following problem occurs. This is consistent across MS MAIL, Lotus Notes, and Groupwise.

Unless you answers YES to the security warning message for at least one of the documents preceding the last, you will never get the message for the last document.  It is necessary for you to answer Yes to the last document for the documents to be mailed.

While sending a document reference, if a wrong recipient is entered and you select the Skip Recipient button, Lotus will error.  Do not use the Skip Recipient button.

Known Issues for 2.0C

This section contains a listing of known issues in PC DOCS OPEN version 2.0c.  The issues are broken down by module, and each one is assigned a unique number.  This information was downloaded directly from our Issue Tracking System, so we apologize for the informal descriptions.  These issues are designated to be fixed in the earliest possible release.

Applications

Ami Pro 3.0/3.01

6400 - when saving a document the user can switch to another document while the first document is still saving and the second  document gets overwritten by the first document.  They say they have a fix and are going to email me a file pcdocs.smm.

5485 - Problem with an AmiPro document "Being Edited" status. To Reproduce, From DOCS Desktop perform search. Launch AmiPro by double clicking AmiPro document from the HITS. Close the document. Highlight the document on the HITLIST.  View document.

6222 - when you close a document in AmiPro and then try to exit PC DOCS, you get a message that says that the document is still open and asks you to save your changes.

6001 - integration with DOCS and AmiPro. When a user selects a DOCS template document for use in AmiPro and they have AmiPro's Autosave function enabled, Autosave overwrites the template document even though the user only has copy rights to the  template file. 

5689 - How do you pull in Objects.,  When she does picture open it brings up a quick retrieve.  Can this be disabled?

5444 - Bring up a quick retrieve. Choose PRINT. It launches AmiPro and then gives the following error...
	Error 51 Macro AUTOEXEC.SMM!DDEPrintRunning not Found. 

3048 - On retrieval of a Password protected file, if the password is entered incorrectly the file is not opened.  On a second attempt to open  the file PC DOCS dialog box tells you the file is "in-use".  Closing PC DOCS Open is the only way to clear the error.

Word 2.0

5293 - When Word 2.0 is integrated and you do a shift save as and select another document format, no conversion takes place.

5694 - When you are in Word 6.0 document and you choose close from the control Panel it asks you if you would like to save this document Yes No Cancel.  If you hit Cancel it doesn't go back to document it closes the document.  It should put you back into the document.

4846 - Created a word document with only 20 characters at first.  Saved it and then pulled up the document again, and added, counting  [END] & [NL], 20 more characters and then saved the document.  The total number of characters came up to be 27.

4057 - Saving to a remote library is not possible in WORD with front-end profiling activated. Creating files on remote libraries.  They have front end profiling activated in WORD and they want the secretary to be able to save to a remote library.  The problem is, that with front-end selected they are forced to fill out profiles.

4147 - Need to show doc name in file menu in word instead of the DOS name (like it does in Excel)

6236 - PC DOCS OPEN/ Word 2.0c File/Insert.  The PC DOCS Dialog box that follows a File/Insert in Word 2.0 does not include the option to link as does the standard MS Word File/Insert Dialog Box.

6032 - When you do File-Print Merge - it doesn't release data files so you have to exit out of both WORD & DOCS to release files.

5636 - After the SHIFT-SAVE AS. THIS IS REPRODUCIBLE WITH WORDINTA.DOC. To Reproduce do the following:  Open an existing profiled document in WORD 2.0.  Do a SHIFT-SAVE AS.  Save the document to the A: drive as a TEXT ONLY file.

5536 - Trying to use a FAX as a print driver in Windows.  He receives a message that says :  Using INTEL SATISFAXTION: "Not compatible with this application."  He is trying to print from Integrated Word and receives this error message  with the FAX  as the printer.

5460 - Profile saves, but document isn't there.  People save with a new profile, but when they go back to retrieve, the file isn't there.  Using MS Word 2.0a.  They do not use shadowing.  Usually, they only use one document at a time. User wonders why OPEN doesn't do any verification.

5359 - When you go into Word. then do PRINT from the FILE menu, and select SETUP to bring up the Print Setup dialog, the SETUP  button there is shaded out when it shouldn't be.

5129 - Problem with version 2.0. They go into Word 2.0c and start a brand new document.  They save the document, and create the profile.  They then copy what they have typed in, go down a few lines and paste the lines.  They then do a SAVE AS and select new version. GP.

5030 - When running WORD60IN.DOT to integrate Word, PCDOCS.INI must be in C:\WINDOWS in order for it to enable Front End Profiling.  This should be changed to search the current working directory, the \PROGS directory, and the path.

4987 - Attempting to exit Word from the print preview screen gives Word Basic error message 'Command is unavailable'.

4054 - Comment all macros so the user can identify the purpose of each one.

4010 - Client wants a way to disable our use of Word summary when saving.  Please make this an option in the application setting for all applications that we do this with.

3230 - He wanted to know about encryption of Word documents (a feature in unintegrated WORD).

3276 - Environment is Novell/Oracle. Client is receiving an intermitted error when doing saves in Word 2.0C stating the following PC DOCS OPEN error UNABLE TO UPDATE TIME STAMP.

3476 - File/Summary Info Statistics are NOT updating with DOCS information. File Name: DOS File name (OK) Directory:  Shows C Drive Shadow location (feed DOCS file information).

Word 6.0

You should not Full Text Index Word 6.0 password protected documents.  If you do, errors will occur.

6016 - GP in pcdocsw.exe at DOCSSQL.DLL 000A:015F when you attempt to save a Word file from within another application.  From inside Watermark, select OLE object and then select Word 6.0 document from the list.  Word 6.0 is launched with a new file menu that is partially integrated.  Selecting File/Update calls a profile to save the file but saving the profile causing a WordBasic Err 1056 - Not a valid filename ().  Click OK to progress through this dialog and PCDOCSW.EXE GP's.  This same scenario happens if you are in Excel and use Insert File to bring in a Word 6.0 document. 

6122 - Document still being edited message.  Users are still receiving message about the DOCUMENT STILL BEING EDITED and that WORD HAS A DOCUMENT OPEN when trying to exit DOCS.  AUTOSAVE is on.  This is a plain vanilla install EXCEPT they are running on NT with MS SQL SERVER and NT as their document server.  One site that is having the problem is WORD 2.0 the other is WORD 6.0.  He is definitely using the 2.0a integration.

5373 - Getting error message in Word 6 integration that says it can't run a macro because it is already running.  Sorry he doesn't have more details.

5524 - In Word, after a View/Master Document, there is a button on the new master document title bar which will insert a subdocument.  User wants Insert Subdocument to be integrated with OPEN.

5355 - INSERT->OBJECT-->At this point choose the "CREATE FORM FILE" folder-->Choose a bitmap from the BITMAP directory under the WINWORD6 directory-->check the "LINK to FILE" option and then choose OK at the Window.  THIS WILL RECREATE the ERROR.

5320 - When in a Word 6 document and do PRINT from the FILE menu, and then choose the PRINTER button.  The OPTIONS button is not available.

5148 - I have found if you go in and out of Word 6.0 several times form DOCS I start getting "out of memory" errors.

6292 - When doing a file save to save a document  then making a change to  the document and doing a file save as and filling out a new profile when it saves it gives a sharing violation on drive c:.

6050 - when saving a new document using shift+save to override PC DOCS integration, word will not save the document with the new filename, it saves the document as the default DOC#.DOC  not only is the filename affected but the path cannot be changed either. 

5971 - When using WORD 60 and using INSERT FILE, DOCS only allows an insert and not a link.  Can the integration be changed?  You do have this option when not integrated with DOCS.

5976 - When she tries to create a data source for a Word 6 merge, it prompts her to save it to disk and not to a profile.  Then, there isn't a way to get that data source into a profile.

5993 - WORD 6.0 INTEGRATION.  Saves a document, has the hour glass on, clicks on the while the hour glass is on the screen, click on  FILE, OPEN.  The WORD BASIC ERROR will appear and the client says they can cause a GP doing this also.

5843 - needs to retrieve a document in MS WORD without going through PC DOCS.

5844 - Client is unable to do a FILE SAVE as in Word 6.0 and save in a different file format.  Client wanted to do a SHIFT+SAVE AS and save as a Word Perfect document.

5864 - No integration with Word 6.0 concerning inserting subdocument on Master document using the icon from the master documents menu bar.  To reproduce problem, chose VIEW/MASTER_DOCUMENT from the menu bar and a new set icons will be added.  Choose INSERT.

5671 - File/Exit, then closing OPEN, OPEN will report an open DDE session. Happens two/three times out of fifteen times. - Chances are this is happening based on the opening of a word 2.0 file into Word.

5672 - When installing Word implementation macro WORDIN60.DOC.  Any customized toolbars are modified, default fonts, default styles aren't kept.

5667 - Running Word 6.0a.  While he is working on a document throughout the day, his resources continually decrease. Also complains that his machine in general has been less stable since using OPEN and 6.0.  He said it was a lot better in Word 2.0.

6641 - In Word 6, File menu shows the last several documents  edited by user.  Word will not open a file if you click on a network pathname.  HOWEVER, IF YOU CLICK ON C: COPY IT WILL RETRIEVE AND A FILE SAVE PRODUCES A NEW PROFILE  INSTEAD OF A RESAVE.  

6463 - Modify the PCDOCS Mail Merge menu item to allow the user to select an Excel data file for merging.  When you select the Mail Merge "helper" supplied with Word 6.0 you can select a data file that is a format other than Word 6.0 (Excel 5.0) is the one I chose.

5031 - MS WORD 6.0 is installed on the server and workstation.  When changing the file location, edit template to the local drive of the standalone WORD 6.0 the network version is also changed.  Is their some INI file that maintains this information?

Excel 4.0

5086 - When a cell is linked with another spreadsheet and the sheets are saved, closed and then reopened the linked cell references the shadow drive.  What happens when a user logs into another PC?  The link will no longer be valid.  This is a problem.

5350 - Passwords in  excel documents.  They imported  excel documents with passwords and now want to remove the passwords and cannot find the passwords with our integration.  This was an oversight by our integration, we have no password option in the DOCSXL40.

5523 - Why do we make user choose a file type when you save as a new version in Excel? This user found it very irritating.  Also, it is inconsistent with our other integration.  Why doesn't Word ask the same question, for  instance?

5973 - In WORD Shift, file close will bypass DOCS, in EXCEL it does not.

5957 - #2 Excel - if you try to add security to a excel document, it fails.  If you save a document w/o security and then resave a version and then add security it works.

5386 - workbooks not saving correctly.  Workbooks created before the Version 2.0 upgrade do not come up on the QUICK RETRIEVE when you have gone in and edited them. 

5772 - I loaded excel locally and opened it without DOCS integration and it took approximately 4 seconds.  I integrated the application and it took about 60 seconds to load excel.  The client says, and I have to agree, this load time seems unreasonable.

6282 - If he has a lotus 123 file and he does a single import unless you save as another profile it will work.  Save as will work but then you will have two profiles  this is because you cannot choose file save as format.  Maintains the lotus format. 

6269 - If a spreadsheet has been checked out/exported and is being accessed by Excel in normal native mode errors occur because of  the AutoClose macro/define name.

6462 - I tested this and I am able to bring in the excel document as the data file.  but  for some reason Word tried to establish a DDE link to excel.

Excel 5.0

6281 - Excel integrated and not able to use security feature correctly.  Client has 2.0a integrated w/ EXCEL 5  when they set security on spreadsheet if you give retrieve rights, view, copy rights not edit  rights w/o edit they cannot edit.

5669 - Opening an Excel document without Excel running returns Error PC DOCS OPEN could not establish a DDE conversation with Excel|System.  The operation could not be completed.

WordPerfect 5.2

6386 - GPF in WP52, When you try to print a document with WP5.2 and you choose Graphics and make a change like DO not Print or set it Draft  and choose print you will get an application error.

3489 - File/Find Files function is not currently integrated with PC DOCS.

4866 - WP6.0 File/Quickfinder:  Takes you to Desktop allows you to select document, but after selecting the document, cant retrieve.  In addition if you select a document that is not a WP6.0 document it launches the application for that document.

6361 - Front end profiling is not working with WP 5.2 when the PCDOCS.INI file is in the \PROGS directory.  I was able to duplicate this error.  With the PCDOCS.INI in the WINDOWS directory front end profiling worked fine.  Moved it to the \PROGS directory on my machine and it fails.

6103 - WordPerfect 5.2 for Windows... When they close a document.  Save the document, etc... They receive the message, when trying to open the document, that the document is being edited.  It is ON and OFF and she cannot reproduce at will, but, it happens. 

6033 -  In WP, When you do Graphics - Figure- Create - File Retrieve, it bypasses DOCS and brings up regular WP file open. However, Graphics - Figure - Retrieve works fine.

5847 - On a group of WP 5.2 documents that are secured for access only by a group, and if a group member is editing it, and someone else tries to edit the document they get the read-only message.

5768 - After Grammatik has been run on a document, there is an option to Save (works fine), disregard (also works fine) or Save As.  If Save As is chosen, a native save as screen is being called. The DOCS save as screen needs to be called so the output can be saved.

5767 - When using Grammatik with WP 5.2, the program will not work if the document you are in is not a saved document.  When you run Grammatik (Tools/Grammatik) WP brings up a native save, this should be a DOCS save.

5635 -  retrieve a graphic In WordPerfect 5.2.  When you retrieve a graphic it brings up a quick retrieve.  You do a GRAPHICS--RETRIEVE and it brings up a QUICK SEARCH.  This should bring up a NATIVE WP retrieve, as does the new WP 6.0 integration.

5587 - She gave several examples of when using passworded document(s) in WP, it would GP.  She gave me one that I was able to recreate.  In WP, type a document and do File/Password and assign a password.  Then File/Save and give it a profile.

5304 - When he goes into WordPerfect 5.2, Open an existing document, modify the existing document, save the document, exit WordPerfect and then launch the document again.  He then tells him that there is already a copy of this document on the Workstation.

5240 - If you launch WP 5.2 from the DOCS desktop either a quick retrieve or a profile search and double clicking a document or hitting OK and then go back to the desktop by doing an  ALT-ESC and launch another WP document, you loose your cursor.

5169 - Front end Profiling won't work with WP52.  We put his PC DOCS.INI FILE in his windows directory and it worked.  There are many firms that are not going to want this file in the users windows directory.  This should be fixed.

4882 - When the client saves a document in WordPerfect 5.2 using the <CTRL><F4> key combination, fills out the profile screen information and presses the OK key (SAVE), then try to retrieve the document from the Quick Retrieve.

4852 - When you create a new document in WP and then do File->Exit, the OK button in the Save options window should have the focus, rather than Cancel.  It should be the same as when you do File->Close.  The message is a WP message and should be a PCDOCS message.

4836 - If you are in WP52 and you choose File/File Manager it takes you to the desktop like it is supposed to do you select a document it then asks you for a launch method even though it is already loaded.

4267 - Word perfect 5.2 macro ?  Create a master documents made up of any sub-documents.  If you go into WP with a blank screen. Go  to tools and choose master document. From here you would choose sub-document, at this point a WP file retrieval screen is pulled.

4061 - When user does an import of a spread sheet into WORD PERFECT it gives them the normal WP file open screen.  There is no integration.

4055 - Comment all macros so the user can identify the purpose of each one.

3737 - File/WP Mail - brings up a native Save As dialog box.  Is this an incorrect WP call or are we intercepting improperly?  Do we plan to integrate with the WP Mail Package??

2761 - The attachments drive letter for the path being stated in the quick retrieve window is incorrect  w/WP using the DocuComp 1.3.  The drive letter is related to the background mapping path where file is a Short  Losing Documents and Edits in WordPerfect.

2777 - This is not a problem with PC DOCS OPEN.  Client wants us to create a program to compare file sizes on every save so they can  be alerted if there is a difference between the local and network copy of the file size.

2796 - The macro that we provide does not allow the user to do a keyboard merge.  They want another macro like the 4.x product has that  would allow for keyboard prompt merging.

2953 - She has documents that were created in WordPerfect 5.2.  If she brings up a document, makes changes and then runs  Grammatik (WordPerfect's built-in grammar check) it brings up a PC DOCS "save as" profile as if it were a new file.  

3042 - WordPerfect PC DOCS integration.  When you highlight a piece of text and hit "save as", should save that piece of text into another document.  Rather than the whole document again.  

3490 - Find Files, File Manager etc. should return the Profile Search NOT the Desktop.  From a Users point of view this is inefficient and  frustrating to say the least.  The user is in WP and intends to use it so obviously does not want it removed.

5858 - cannot get integration to turn off. With WP5.2 he can disable and enable PCDOCS with WP 6.0a he cannot get PCDOCS to disable.

5623 - Word Perfect 6.0 with PC DOCS 2.0a Upgraded to 2.0a and now when exits DOCS he gets a GP.  It works fine with out PC DOCS. He called back and stated that exit from menu works w/o GP if you click on the control menu then he sees the GP.

5427 - Using Front End Profiling , when you do a File New and then cancel the profile you are returned to an empty document 2 in WP. This effectively negates Front End Profiling.

3175 - Our WP integration macros are not supporting WP backup files.  If backup files exist (bk1, etch) WP will prompt the user to retrieve them.  With DOCS active the user is never prompted for these and could lose their changes with the backup file not being retrieved.

WordPerfect 6.0

6358 - After using the disable macro to unintegrate, DOCS is still called when doing a file/exit.  There is a profiled document on screen that had been edited.  The disable macro is played to unintegrate the application.  However, when you do a file/exit, a DOCS prompt to save messages is still getting called.  This only happens on when doing an exit (close works fine and all the other features seem to be unintegrated as well).

When printing multiple documents from the Desktop there is a 5 second delay between documents.  This prevents WP 6.0's printing module from interfering with PC DOCS.  Users printing multiple large documents from the Desktop may still experience problems.  Please advise users to print large documents individually, rather than grouping them first and then printing them from the Desktop.

6355 - Access Denied Error message on Save - User 1 is in edit mode, User 2 opens in read only.  As long as User 2 maintains the read only copy on screen, User 1 cannot save.  WPWin Error - Access Denied.

5906 - This is how he  causes the GP.  Go into WP with a windows printer driver installed as the default printer.  Type some text in a document, do a FILE, SELECT PRINTER, change the printer to a WP PRINTER, go back type some more text, and then change the driver.

5792 - File/Template is not integrated.  Allows a file/new without calling a profile.  File/Template acts as the same as a file/new with a multitude of template choices.  Even though FRONT END PROFILING is established, the user can create a document without a profile.

6000 - In WP choosing FILE, COMPARE DOCUMENT, ADD MARKINGS, we then immediately bring up a quick retrieve list for the user to choose from.  Unfortunately, without integration WP gives the user 3 choices after choosing OK.

5747 - The integration for WP 6.0 overrides the bif files environment setting making impossible to turn off/on fields.  Example is the "Display Help Prompts".  If WP is unintegrated you may turn this off in bifedit and it will stay off.  If it is integrated, the "Display Help Prompts" are always "ON" when you enter WP.

6212 - WP with 6.0a file you can't save in another format.  could it be possible to save with a new file format?

6160 - Wp60a mail merge loses DOCS integration.  Do a TOOLS, MERGE, MERGE, CLICK ON ARROW, SELECT FILE, bypasses integration.

6014 - integration with WP 6  master doc file option.  in WP6 in file menu you can call master doc then sub doc.  when you do this it brings up a WordPerfect file screen.  It should bring up the DOCS Retrieve.

5731 - Can't start WP6.0 when using the backup feature after the PC locked up. Client can't start WP6.0 from the OPEN desktop when using the backup feature after rebooting the PC from a lockup.  OPEN's integration doesn't recognize that the backup utility is being used to look for that file.

6262 - She has a network copy of WP 6.0a installed on her network, but only one person at a  time could get in to use WP.  She kept getting a bif editor busy.

5349 - Customer is concerned with speed of execution for macros when comparing WP6.0 with and without OPEN integration.  Also, is there any way to avoid users getting ahead of integration.  They have OPEN and CLOSE icons on a power button bar.

4794 - If you have a profiled document and you use the shift-saveAs key to save the document in order to get the password option it will save the document with a password.  When you go to exit however, it will ask you again if you want to save the changes.

4397 - If you save a document using the non-integration shift-SaveAs combination.  Then type a few more characters and then go under  file and choose the exit option, it immediately brings up a profile.  It should bring up the question of do you want to save the document.

4041 - File Exit is not prompting for "do you want to save your changes to the document"  Instead the file is saved without prompting the user.  This is not good.  Then the file is locked which means you will get the "file is being edited" message when you try to open it.

3547 - This is a great enhancement request.  Currently we do not insert the Description field into the Doc Summary and this should be done ASAP even if the "linking" must wait for a later release.

Quattro Pro 5.0

4053 - Comment all macros so the user can identify the purpose of each one.

Lotus 123

5344 - The Lotus File Save smart Icon is not integrated. Lotus 123 release 4, Saves Smart Icon for File Save doesn't work bring up the quick retrieve screen.  This icon should be integrated!!!

5530 - Incorrect password does not release file from DOCS.  User must exit Lotus to try again. - Re-entered as a pending enhancement waiting for Lotus technology to catch up.

4052 - Comment all macros so the user can identify the purpose of each one.

MS Mail

7174 - Mailing Multiple Secured Documents.  When multiple secured documents are selected to be mailed, the following problem occurs. This is consistent across MS MAIL, Lotus Notes, and Groupwise.

Unless you answers YES to the security warning message for at least one of the documents preceding the last, you will never get the message for the last document.  It is necessary for you to answer Yes to the last document for the documents to be mailed.

7095 - When a mail reference is opened, a hitlist is displayed.  Occasionally (only happens on some machines...), pressing Cancel immediately after the hitlist displays causes a GP in docsfrm.dll

5502 - Microsoft Mail does not save attachments.  It's functionality right now is simply being able to attach files and save files from the  DOCS interface.

5549 - When mailing references to database files - Recipient of the mail needs a way to identify which database the file is referencing.  When the recipient is not attached to the proper database the document is searched.

5795 - MS mail integration and full text editor.  We cannot view MS MAIL documents in our viewer and therefore, we cannot fulltext index the documents.  The ENHANCEMENT REQUEST is that our viewer have the ability to view and fulltext the MS MAIL.

5871 - They want to have the document name at the bottom of the icon in the MSMAIL messages when a document is sent from DOCS.

6029 - They want to be able to route a document to multiple people and have them make changes and then have the routing continue.  DOCS does not give the user the option of attaching a reference to the document it automatically loads a new profile.

5875 - Using w/ MSWORD & MS MAIL and having problems.  If he attaches a document and wants to send it to different people, the next person edits it, saves it and DOCS profiles it as a new document.  There is no way with existing integration to make  modifications.

6365 - When you choose mail it will ask you if you would like to select versions.  And you Select Versions it will only let you select one version.

6388 - Have a Banyan server set up with Microsoft Mail using the special integration provided by Banyan.  Have tried setting up the integration with DOCS using savemsg.dll, this does not work.  When trying to save to PCDOCS you receive an internal error.

6389 - Does PCDOCS have any plans to integrate with Banyan Vines native mail application?  If so, what would be the likely timeframe? Do you know of any other sites with this or similar requirements?

CompareRite

4761 - CompareRite - Not releasing documents properly on an attachment process, file cannot be overwritten. CompareRite's attachment file created with the RED extension cannot be overwritten at the DOS level.  Un-integrated CompareRite overwrites this file without a problem, DOCS is not releasing the document for further editing so I can only assume it is also blocking the overwriting of this file.

3607 - When you run CompareRite from OPEN, if there is an error in the compare, and it doesn't create the resulting document, OPEN still puts an entry in as if it worked successfully.

Database Import

6061 - Cannot import real numbers.  I set up a custom table through Designer.  The table had an edit field defined as being a real number.  Database Import does not import the value to the right of the decimal.  For example, if 20.333 is to be imported, then 20.000 is what gets imported. 

Downloading large numbers of clients, matters, or other verification information (greater than 150 rows) may result in a SQL error.  The workaround is to download the information in relatively small batches of 75 - 100 rows.

DOCS Designer

4832 - You can not create a Hit List that displays user defined columns in the list box.  An error will occur.

5687 - You can not have a radio group in a profile search.  If you do, PC DOCS will be unable to find any of your documents.

6083 - Status column on QBE works funny.  combo box stays open when select, enters value not the selection, and cannot be added to an existing QBE that has been through an upgrade.  Question about checked out documents
Wants to locate all the documents whose status is checked out.  however when she enters the checked out she gets error trying to convert varchar to int.  if she enters 3 which is the value for checked out status she gets the same error because the column is an edit column.  I tested in 2.0a and the column has a combo box and I select checked out...when I select checked out the combo box stays open (no. 1) and a 3 is entered into the column on the QBE.  the search goes off without a hitch.  Customer tried this on her 2.0a QBE but the combo box wasn't there.  You cannot click and drag the status column over and have it work.  Like Storage type you have to copy it off another form so we had to go out and flag the status field not protected in DOCSCOLUMN and then delete it off her QBE form and cut and paste it from the default QBE form that we created when she upgraded. 

6196 - In Designer, if you pull up the LAWPROF profile to edit, you can delete the full text index checkbox off of the form.  If you save that form an attempt to use it, you will get a GP in Desktop.  To reproduce the GP, edit the LAWPROF form, deleting the full text index checkbox.  Next, set the form to be the profile form used for your group.  Go into Desktop and do a profile search.  From the hit list box, choose a document and attempt to display the profile.  On the attempt, a GP occurs in PCDOCSW.EXE.
An interesting tidbit, if you place the full text edit checkbox back on the profile form, it can no longer be deleted (You get a message saying the field is protected and cannot be deleted).  Also, once the field is back on the form, the GP no longer occurs in Desktop. 

4993 - Maintenance Forms GP when built on a lookup containing a Filter. We had this problem in 1.0 OPEN and was fixed in 1.1.  When you build a table in designer it prompts you to build a lookup for that table.  If at that time you also place a filter on that table, and then build the maintenance form on that lookup, the form will GP inside of LIBRARY MAINTENANCE.  The way to work around this is to create two lookups.  One that does not contain the filter and that the maintenance form is built on and another that has the filter that is used for lookups from other forms 

6127 - Radio Group Object Items:  According to our documentation, object items are added to a radio group by placing the items on separate lines in the object items field (p5-6).  We need to add that to get to the next line, the user needs to <CTRL>Enter.,Radio Group Object Items:  According to our documentation, object items are added to a radio group by placing the items on separate lines in the object items field (p5-6).  We need to add that to get to the next line, the user needs to <CTRL>Enter 

5686 - If you have radio buttons on your profile, and you edit your users defaults, it will not save the entries for the radio buttons in the PROF_DEFAULTS fields of the people.  Instead it will refer to a column "null".

Desktop

6038 - Placing an apostrophe (') in the "Open Document" field in the Quick Retrieve causes an SQL error.  For example, Typing "Hugh's Document" in the Quick Retrieve will cause an error.  However, doing a profile search for "Hugh's Document" isn't a problem.

6069 - DEC PathWorks 5.0...  Not able to retrieve a document that has had Security applied to it from the Desktop.  We checked the rights at the Lanman level and they were correct...  but at the Desktop, I could not even retrieve my document..... we checked the right at the VMS level and found that there is some difference at this level between files....  I have copies of this file information if needed. 

5956 - If you don't add a trustee to ALL files you import with document import, OPEN removes the create right from Docs_users in the subdirectory where you are importing documents.  If you add a user (like give all rights to docs_users) it works fine.

5796 - I ran a test at the desktop and tried to delete one of my documents.  I did the delete and it disappeared from my quick retrieve.  However, when I did a search for that document name it was still there.  Even worse the status of the document was Available.  I tried to retrieve and I did receive an error saying that the document could not be located. 

6048 - Profile search GPs on close when the Desktop thinks it has a valid connection to Sybase remote libraries from the Oracle library but doesn't. Setup is: Oracle library with a couple Sybase/Sun libraries as remote libraries.  Pre-connect to search libraries is Yes.  Go into desktop, do a profile search returning all rows, and click close on the hit list form.  GPs every time until the desktop figures out there is no connection there to close.  You can convince the desktop there's no connection to close by ignoring the GPs.  Subsequent searches/close tests work fine.  See Doug for more info.  Workaround is to set preconnect to No. 

5757 - When they do a file save and save a document then make some modifications to then do a file save as to save it as a new version,  then they do a file shift save as and save the document to the local drive as a DOS text document they get a sharing violation on drive c:.

6108 - When saving files that the user does not have control (permission) access to, getting error "Trustees not successfully applied." User reported strange problem that I have been able to somewhat reproduce in-house.  He originally reported a whole sequence of steps to cause the problem, but I've gotten it down to the following steps: User A creates a doc and assigns Normal Access to DOCS_USERS.  User B opens the document, edits it, and does a Save. at this point I get the "Trustees not applied.." error, but Mike doesn't get it until he does a second save.  This is not necessarily a huge problem because it appears that the error is happening because the trustees are already applied to the file (and since they are, user B doesn't have the rights to change the access control list for the file...)

6116 - If you use a billable Matter when filling out a new profile, or changing the Matter ID of an existing profile, the Billable checkbox does not get checked. 

6169 - Getting DB_INIT error login into DOCS. Caller receiving error DB_INIT HAS NOT BEEN CALLED BEFORE ACCESSING DBLIB.  DB_INIT AND DB_FINI SHOULD BE CALLED BY USER BEFORE AND AFTER USING DBLIB.  Once the caller receives this message and chooses CLOSE, she receives a GPF.  She receives these messages while trying to run the DESKTOP while she is not logged into the network  She is running WATCOM 3.1 which is launched in her STARTUP GROUP and a database locally.  When she is logged into the network, she runs fine --->  She is able to open up the database.  Her PCDOCS.INI file used both the STANDALONE and her USER_ID  in the [STANDALONE] section.  Neither worked.  When she changed her WINDOWS setup to NO NETWORK INSTALLED, it worked fine --> as opposed to using the NOVELL NETWARE (SHELL VERSION 3.x and higher.)  User should not need to be logged into the network to run a WATCOM database.

4562 - If you are low on memory (for example if you have a bunch of New Project windows open), The desktop frequently GP's rather than giving you out of memory errors when you attempt to open a new window or do something else that sucks up memory.

5159 - Multiple document selection for open.  When the file does not exist at the DOS level the application (WP60) is launched anyway and not message is given as to why the documents were not opened. Multiple document selection for open.  When the file does not exist at the DOS level the application (WP60) is launched anyway and not message is given as to why the documents were not opened.  If one of these documents is selected a PC DOCS message that the file cannot be found is displayed.  This message should also display when multiple documents are requested.

5787 - If you have Duplicate Document Names OK and then do a search from a Project for document name 'testing', and then try to add more than one of them to a project, when you select the second one the OK button gets grayed. If you have Duplicate Document Names OK and then do a search from a Project for document name 'testing', and then try to add more than one of them to a project, when you select the second one the OK button gets grayed.  If you do a Profile Search and then select the documents and drag them to the Project they get added without a problem, it is only if you do a search within the Project.

5454 - Problems with the filing scheme changing with existing documents under the old scheme. When the filing scheme changes, the network copy retains the old filing scheme for a new version,  but the shadowed copy changes.

5756 - PC DOCS Desktop cannot be closed after a multi-version print from desktop QR.   I selected a document that had two versions.  Version one is password protected, version two was not.  I also have popup network messages running.  The first document process went without error.  Just before I got the launch request for the second version the first popup message appeared. I clicked through it.  Word 6.0 was left open on screen with no document, I had an hourglass and after several minutes got a message from Word stating that the process was taking longer than expected did I want to continue waiting?  I answered Yes and the message never cleared.

5765 - Date and time on SHADOW Documents are being set to September 16, 2024.  The date on the local system is correct.  They do not know where the date is coming from.  Windows for Workgroups 3.11 and NTAS.

5298 - Banyan 5.5 connecting to Sybase on Sequent.  Users GP every time they exit Windows while DOCS is still loaded.  We need to pick up the windows "close event" command so Windows will prompt the users to close DOCS when it is running, instead of hanging the workstation.

6285 - Focus Bar problems.  He found an inconsistency in 2.0a project folder procedure.  When you select project from options menu & click on add and select sub-project, PC DOCS presents a scroll down window with all folders to be selected.  The first folder is highlighted, but when you select the file you want and click on add, it adds both of the files.

6301 - If I do Document->Copy and save the document to a remote library, a Copy To action does not get saved in History.

6276 - From the desktop I did a File/Import File from the a drive.  Then I remove the disk in the a: and try to open an application.  for some reason DOCS OPEN looks at the a:.  WHY!!!,  When I import a spreadsheet to PC DOCS from drive A: PC DOCS accesses drive A continuously.  Each time I open the spreadsheet PC DOCS will try and access the A drive until I import an other file from the C drive then it no longer searches for the A drive.  Can someone look into this and see if this is a registered issue and let me know because several sites have reported this issue occurrence also a new site is going to be doing all their imports form floppy disk so I need some sort of answer ASAP.

6246 - If a customized hit list does not include a column from a foreign table, then an SQL error occurs when attempting to do a profile search using full text searching.  To reproduce this error: In Designer, copy the standard hit list form and edit out the application and author columns.  Save the edited form as a new form. Set the form to be the one used in Desktop (through library maintenance).  In Desktop, do a profile search using full text searching. The error is #156 incorrect syntax near the word "AND".

6265 - A "BILLABLE" column needs to be added to the versions table to be used in recording activities correctly in the activity log. To correctly fix the billable problem addressed in Issue 5682.  Several other issues I've entered deal with the fact that things are taken from the profile when they should use the version table.  i.e. error messages, storman activities (archived, deleted, etc.).

6213 -You can choose template as a storage type even if you do not have rights to do so.

6364 - When you have a group in profile defaults, whose name does not match the actual network group name, OPEN will give an error "One or more of the users in the access control list is not a valid user on the document server."  The same group, when assigned manually and not under user profile defaults, will work fine. 

6370 - When printing from the desktop - An extra Access entry is placed in the History.  The first access does not indicate a version number.  The print and final access entry indicate the version number printed.  When printing from the desktop - An extra Access entry is placed in the History.  The first access does not indicate a version number.  The print and final access entry indicate the version number printed.

4503 - Add the ability at save time to put a document/profile in a project.  In this way, the user does not have to pull up the project screen  to add a document to a project.

3906 - If I assign security to the new profile on a copy, the security is never added at the file level.

4859 - Using 1000 user copy of 3.11 Netware.  Noticed a problem that shows up a lot when software is incompatible with this flavor of NetWare.  Or software thinks that any user that is logged in as user number 256 or greater is really the user that is logged in.

6807 - Users are doing the following:  Quick Retrieve, Search, Enter in a name and click OK., Returns nothing be cause name was misspelled, Correct name and search again., Hit list is grayed out on results screen.

6594 - having problems with a DOCS supervisor accessing a secured document. Running Lan Man  NT SQL Server Document server is a LAN MANAGER. HE is a DOCS Supervisor.

6623 - She says that if using an application that uses directory monitoring you can open the document work on it then close it.  Then if you minimize the application and try and launch the same document again it will give you an error that you are already editing.

6441 - There is an issue in DOCS 2.0 and 2.0a pertaining to security.  When a document is secured users that want to view or open the  document must have edit rights.

6317 - If a user loses connection to the system while editing an AmiPro document, the lock file does not get removed and the status stays "Being Edited".  Currently, the only way to correct this is to delete the lock files and manually update the database.

6224 - Running DOCS 2.0a with Oracle 7 on SUN Solaris.  Seems that all data is in Upper case letters even though some are entered in as lower case.  Example, file out profile with document name as "Oracle Test", this will appear in database.

6092 - Word macro for Title Bar; wants to show drive letter and full path in the title bar, just as you see on Window menu.

5955 -  After that, we looked at the SQL log to see what the system was doing with the quick search information.  ANSI doesn't define a string type past 256 characters, so each SQL vendor is free to make up their own type.

5947 - saving of profile search for quick search is hosed. Client has problems when he does a profile search from the desktop and then saves the results.  When he goes back to reissue the query from the saved icon on the desktop client gets a dialog box.

5790 - They edit a bunch of documents and then at some point they run out of memory.  He is sending a FAX...  I have the fax and will  try to reproduce shortly.

5713 - Here is a list of the DLLs that we are shipping and the versions that are on the latest SDK CD from Novell.  We need to ship these with the product as soon as we can.  Our clients are already using some of these and we are not keeping up with Novell.

5548 - Is there a problem running on a 1000 user copy of NetWare.  used to be on a 250 copy of NetWare but never experienced the problem.  only happens when users exceeds 256. 

5352 - It then attempts to index all the way to the end and then will restart from the document that was secured and you get a GP in Infolink dll.

5149 - I created a new project and went to add a document.  When I added a document it appeared twice in the project window.  If I  deleted one instance of the document from the project everything looked OK.

5171 - The desktop needs to be modified to allow WP60 file viewer function to be used when the user tries to view a WP6.0 file ONLY....

5172 - The file viewer in WP6.0 must be used whenever the user tries to view a WP6.0 file.

5104 - Have the WP header be modifiable.  He like the when it said UNMODIFIED or MODIFIED and if you would be able to put different info in the header.  When I talk about the header I mean where it says: WORD PERFECT.

4883 - When a user tries to retrieve a document that they had just saved, the message DOCUMENT IS BEING EDITED.  When the client saves a document in WordPerfect 5.2 using the <CTRL><F4> key combination, fills out the profile screen information and presses the OK key (SAVE), then try to retrieve the document from the Recently Edited Documents list.

Cost Recovery

7175 - Using Cost Recovery with Quick Save On. Keystroke counts are not recording correctly when new versions are created after interim saves.  Edit a document adding keystrokes, select File/Save.  Add no further keystrokes, Select File/Save As to New Version - An edit entry is entered showing all keystrokes - New version shows keystrokes duplicated from edit line of previous version save.  On the other side, if you edit version 2 and use interim save, add keystrokes not intended for version 2 and select save as to new version.  Both the edit line of Version 2 and the version 3 line will show the entire count of keystrokes.  This is "overstating" the total keystrokes in each of the documents.  The grand total of keystrokes is wrong because the same 45 keystrokes are added in again for each version saved.

5854 - When printing multiple versions from desktop only the first version is recorded in the activity log.  From desktop I printed versions 2A, 2B, & 3 after 2B & 3 One time, I got the message do you want to save changes I selected no and when I ran the Cost recovery report the pages for versions 2B and 3 did not appear.  The save attempted to save as a new document before I canceled.  by looking at the actual entries in the activity log The last 2 DOCS did not appear.  The pages printed as expected. Subversions were still not recorded and I never got the save message as above 

6077 - Time is reported in seconds and should be converted to minutes.  This is always a problem when explaining this module in training.  This has also been reported from customer sites who feel it is inconsistent to see the time in minutes in activity but not get the same conversions in Cost Recovery.

5027 - Ran a COST RECOVERY report and found unrealistic information concerning pages printed.  Their is a total of 2 records that were found.  One record is on ZEUS and one record on the QAPROD database with an unresonable print count of 65534.

Storage Management

5018 - When a document and activity log are moved to another library the activity log is copied to the new library so customers could be double billed when cost recovery is run.   I had a question from training on what exactly happened to the activity log during a move.  So I moved a document w/log to another library and found I had duplicate records because it was copied.  This leaves an area where customers can be double billed for time or pages printed until the profiles and activity log are deleted from the original library.

6080 - Deleted Documents are left as status available in the versions table and no deleted entry is put in the activity log for the deleted versions.  I was testing the deleting versions and keeping the profile,  The correct number of versions are kept at the DOS level; however, DOCS makes no record of the deleted versions and if you attempt to open the deleted version from the desktop you the file not found error message.  If all versions are deleted then the profile is set to deleted, but the versions table still have status as available.

6186 - Moving documents and profiles to another library leaves the profile record in the current library and the STATUS is NOT AVAILABLE.  The profile should say something other than NOT AVAILABLE.  It should say something like MOVED TO OTHER LIBRARY or a message that means that the document has been moved. This is how Storman works.  When Documents are moved to another lib the profile is maintained on the current lib with the status of not available.  The last entry in the activity log will be moved to.  Attempting to open the moved document in the original lib will give a message telling the user where the document was moved.  i.e. This document was moved to #465 on lib REMOTE lib.  If the activity log was not moved it is needed for cost tracking.  When the data is no longer needed on the original lib the profiles can be deleted though Storman.

5397 - If you save a document then modify only the profile of a document and change the storage type to archive and retention days to 10 and save the  profile the process_date is not changed in the profile table.  This means that you have the ability  to archive a document before the intended archive date.

6020 - Deleting documents when they are deleting documents and it doesn't go by last edit date it is going by last accessed.  The documentation says it will be archived from the last EDIT date.  also when you delete the documents. the documents on the profile say unavailable and when try to  launch it says try back in a few minutes.  It should say that the document has been deleted.  They are not even able to do a document profile search on status=deleted.

5336 - If user moves documents between document servers they get an error message: UNABLE TO SECURE DESTINATION DOCUMENT WHEN MOVING DOCUMENT (docnumber).  The document servers are Banyan.  I can reproduce this error here as well. Suggested adding section in PC DOCS.INI  [network] VinesFileSecurity=No      This problem is happening because they don't have the Banyan File Services module that will ship with 2.0a.

5770 - When moving a document with StorMan to another document server it sets the data and time of the file to the current date and time.  It does not retain the date and time of the file.

6270 - PROFILE SEARCH and SEARCH RESULTS  windows appear off of the screen useable screen area in STORMAN when windows are not maximized.  I had both DOCS OPEN and STORMAN open at the same time with the STORMAN window on the upper portion of the screen.  When performing a search using the PROFILE SEARCH icon, the profile window appears only partially on the screen.  The only way that I have found to enter information in the hidden fields is to cancel the search, close DOCS OPEN, then go back and maximize STORMAN.  From this point I was able to complete the search.  I also found it impossible to alter the size of the search window to display the hidden fields.  This also occurs with the SEARCH RESULTS window under the same configurations.

When a document and activity log are moved to another library, the activity log is copied (rather than moved) to the new library so double billing could occur if the Cost Recovery module is run before the profiles and activity log are deleted from the original library.

5642 - The performance of the document moves dropped off dramatically on the 2.0A production code.  It takes almost exactly the same amount of time to move documents from blaster/vol1: -> blaster/sys: as it does to move documents and profiles between libs.

5714 - We need to have access to secured documents on Banyan Vines for Moving, Archiving and Deleting.  There is nothing which compares to Novell Supervisor, so we must provide a programming solution so secured documents can be managed with the Storage Management Utility.

Document Import

6402 - The default value of %wp_account does not work......I tried to import a set that was to import the Client ID and Matter IDs from the WP 5.2 document summary.  In the import set I used the variable %wp_account[1000] for the Client ID and %wp_subject for the Matter ID.  In the document I put a value (1000) in the subject field but left the account field blank.  Whenever the field is left blank, it is supposed to put the default value in it's place.  Well, it is not doing this.  It is importing nothing for the Client ID (blank).  The default is not working.

6057 -Access to one set will stick and give the same Access to the next set created......I created a Set in Doc Import and gave Access to a couple additional people besides me.  I then proceeded and created another set.  I checked the Access to this set and found out the Access, which should have been just me, was given to me and the couple additional people.

4867 - When importing documents and specifying a valid drive letter and path to the documents to be imported you get an error back saying unable to create object.  the object name is the path to the imported document.  Were able to get working by using the UNC.  When importing documents and specifying a valid drive letter and path to the documents to be imported you get an error back saying unable to create object.  the object name is the path to the imported document.  Were able to get it working by using the UNC path.  \\servername\sharename\path

5898 - Importing negative number documents from ASCII......I was importing documents from ASCII and had in my profile.txt a -10 as the document number.  It imported -10 as the doc #.  Now when I try to delete the document it will GP on me.

5886 - If multiple people are doing document import at the same time.  Apparently the document number table gets corrupted because after doing the import next document that it tries to save the program tries to use a number that is already in use.  In other words it tries to save it as document 37 and 40 is the next available number.  Going in and resetting the document number to a latter number fixes the problem.

In Document Import when setting document access using %AUTHOR, you must verify that the %AUTHOR value is valid Network Operating System user.

In Document Import when setting %NOS_DIR_ACL, the directory level must be enclosed in brackets [ ].  For example:
If the directory level structure looks like this:
\user\s_smith\plans\*.*
and you want to secure the directory "plans" then the setting for %NOS_DIR_ACL would look like the following:
%NOS_DIR_ACL[3]

6312 - When using the %WORD variables with WORD60 documents the text being imported is garbage i.e. XXXXX or YYYY or combinations of letters.  I will test on some WORD60 documents and try to recreate.

6293 - Cannot use WORD60a summary fields when doing a document import.  When you reference these fields you get garbage in the columns. i.e. xxxxxx or yyyyy or various combinations.

6072 - Most of the changes made to Document Import for V2.0b need to be merged into the main stream.

5889 - They did a document import with 17,000 records and only about 9,000 were imported.  Of all the 9.000 they all have the same parent/child entries, the system put the first value in all profile records for each one.

5625 - GPF's.  Not reproducible and intermittent.  Many workstations.  Using Word 2.0c.  Attempting to do a document import at a user workstation, leaves Document Import, does a profile search after the unsuccessful import and tried to relaunch Document Import, GP's.  

5440 - Can't run Doc Import again after a Nasty GP-.....  After I ran a few imports, i came upon a GP.. I had to re-boot my machine..  when I got back into Windows, and tried to run Document Import again, the hourglass came up for a few seconds, then NOTHING.

5375 - No documentation for the OLE variables in Doc Import...  Are we just going to send this out without documentation for those Word 60  users to figure out? 4/6-OLE variables will get Author, Title, Comments, etc  out of OLE 2.0 Compound Documents.

5379 - Using %WP,%AMIPRO, %WORD variables with a default value does not allow Multiple variables....  You can have these multiple  variables in a field, but when you give it a default value []... it will then give you error saying "a value was found after the default."

4841 - Error Unable to create file object then path to the document. He checked Rights and he had all the rights possible to  everywhere on the network.  When he entered the UNC as opposed to a drive letter the import worked.

Full Text Indexer

Do a fulltext search to display a hitlist.  Occasionally (doesn't always happen), pressing Cancel immediately after the hitlist displays causes a GP in docsfrm.dll

6064 - Searching using the 'not' does not work.....I imported documents with the phrase 'document#' in it where # equals 0 to 9 for 10 documents.  I then ran Indexer with Phrase and Proximity and Index Numbers marked.  I re-initialized and indexer ran fine.  I then proceeded to do a full text search with 'document1' and it returned 1 document.  I then tried to do a search with 'not document1'.  It takes about 2 minutes and then it tells me that no documents fit the search criteria

6366 - Pathworks 5.0 -- when using the lookup to assign the path  "\\JULIET\C$" is inserted in the index file location without the space between the drive name and the path which is needed for the generic drivers.  We were setting up indexer and got the message unable to map a drive message. when we tried to run indexer.  Manually inserting a space to define the break between the drive description and the file path solves this problem; however, DOCS should be able to determine if the generic driver is used and insert a space for the user.

If you obtain the error "Cannot find OLE2.DLL" and are using a dedicated indexing workstation with no Microsoft applications installed, copy this file into the \WINDOWS\SYSTEM directory of the indexing workstation.  You will find this file in the \WINDOWS\SYSTEM directory of any workstation with a Microsoft Windows application, such as Word or Excel, installed.

In some extreme circumstances, if you are importing, indexing and deleting large volumes of documents simultaneously the indexer may return a SQL id error number five or six.  If you get this error click on the OK button and the indexing process will continue normally.

6569 - Can't index very large docnumbers like 10000000.....I imported document numbers 10000000 to 10000003 and they imported fine.  I ran Indexer and it locks up when it finally reaches 10 million.

6653 - Using 2.0b and getting indexer errors and GPF's.  They have a WFW network with NTAS servers running MSSQL.  The full text indexer gives errors "Unable to map to drive" in the indexer status section and it mapped okay then.  Profile searches get GPF's.

6349 - When Indexer is running, I am unable to do a Full Text Search.  I am getting sharing violations.....I had one computer running Indexer.  I was on another machine and did a Full Text Search.  I get a sharing violation.

6259 - Hit list on full text index shows document but unable to determine which version the key word is in.  For example the client does a full text search on wine.  There are three versions of the document.  Only version 2 has the word wine. 

Library Maintenance

4974 - User has experienced corruption in the launch method where information that was in one field was moved to another field or some of the characters just changed without any intervention from the user. Corruption refers to the data being scrambled inside a record for both Launch_methods and for Apps.  This can be so severe as to prevent use of the application .  However, it only seems to happen to WATCOM databases.  I have seen one record of each table corrupt for every WATCOM upgrade I have done (4) it did not seem to happen for the Sybase UNIX, Sybase NLM or NT upgrades. A new requirement with V2.0 was to update all DDE settings for launch methods during install.  This was to have been documented somewhere.  If this is the information you are talking about that is changing, then this is a "feature", not a bug.  If it is something else, please be specific and explain how to reproduce this.

4842 - When use sync users or groups or add a user then use the lookup to identify existing users it sees the server OK but is unable to access the ACL.  This problem manifests itself in both the install and library Maintenance synchronize.  and is specific to Lan Man.  This problem is Lan Man 2.2. specific  can't import users on install  or synchronize users in lib Maintenance.

5512 - OPEN needs to synchronize with Novell 4.0 Organizational Units.  Drop the "group" metaphor and use "Organization Units" when the operating system is NetWare 4

6170 - When doing matter maintenance, used to be able to click new.  Enter the new matte, hit enter for OK then C (for close) then hit enter and would allow entry of new matter all over again.  Now the C doesn't work.  Instead it enters a C in the Client ID field and deletes what you just put in there.  Seems only to respond to the mouse.

6354 - If you click on a flag in library maintenance and type "Y", the flag changes to "Yes".  Subsequent attempts to change the flag using the hot keys "Y" and "N: the hot keys have no effect.  For example, check out the Document Check Out flag in the System Parameters/Features screen.  Click on the flag.  Type "N".  The flag changes to "No".  Type "Y".  Nothing happens.

6089 - Mobile shows Make Check-out Fields Read Only default as Yes, but it defaults to No. 

5777 - Directory monitoring the option is to select to monitor the subdirectories doesn't work.

6227 - Short  Turn Off Searching Primary Library Client is unable to turn off searching of primary library.

6773 - When doing a Synchronization (USERS and/or GROUPS) the first time it works...  after a fresh database is created.... but then....  not again.. All Groups and USERS added to the Netware TREE...  Must be added manually to the DOCS database....

6640 - Creating Primary Group under People maintenance - specifying a primary group other than DOC_USERS - by department -  encountering - security question lawyer giving rights to department [read/view copy] sec [full access].

6539 - 2.0a  Banyan Vines and NT SQL Server. Parsing the Vines user names in a strange format.  The short name is becoming their full name,  Full name is coming in as their extension, network id is the only one working.

PC DOCS Mobile

The Library Maintenance, System Parameters, Features setting "Allow Others to Check In Documents" does not affect Mobile.  If two or more mobile users share the same laptop, they can check documents in for each other even if the flag is set.

4906 - Mobile asks you repeatedly if you want to delete the mobile copies of the documents if you cancel the check in process in the middle of a batch. Mobile processes checking in documents in batches of 75.  If you cancel the check in process, mobile performs the end-of-batch tasks, asking the user if they want to delete the mobile copies of the documents just checked back in.  No matter whether the users clicks on yes or no, mobile asks again, once for each remaining batch to be processed.  If the user is attempting to check in a very large number of documents, this looks like an infinite loop (even though it really isn't).  For example, say the user is attempting to check in 600 DOCS.  That's 8 batches.  On doc number 10, the user clicks cancel.  This was the first batch.  Mobile asks the user if they want to delete the mobile copies.  The user selects yes or no.  Mobile then asks the user the same question 7 more times

5561 - Create a new paper document profile in mobile mode.  Go into docking mode.  Highlight your new profile and click on check in.  The document is checked in.  Exit docking mode.  Go back into docking mode.  The paper document profile still appears in the list of items to be checked in.  If you attempt to check it in, it checks in again.  If you do a profile search on the document name, you'll find that the document appears twice.  Apparently the profile checks in fine but doesn't tell mobile the document has been checked in.

6381 - Cannot download large numbers of clients (or presumably other lookup data to mobile),Created 450 clients.  Highlighted them all.  Received a message from Oracle:  maximum number of enhancements in a list is 254.  This is not Oracle specific...large number of client downloads also cause Sybase to freak out.  See attached pictures for more information.

5879 - Cannot create paper documents in mobile mode and bring them into docking mode. In mobile mode, create a paper profile.  Go into docking mode and attempt to check it in.  Docking mode doesn't realize it's a paper document and doesn't give you the option of paper under storage types.  May be related to issue #5561.

6352 - Downloading users does not update password. When you download a user in mobile, everything, including the password, is downloaded.  If you then try to re-download the user information, nothing is updated.  This is related to an existing issue where launch methods don't get updated.  The problem is that if the user forgets their password, there is no way to reset it within PC DOCS.  You can use SQL to find out what the password is and/or update it, or you can re-moblinst to clear out the existing mobile database, but you cannot use mobile desktop to change the password, even if you are a supervisor.  This bug cannot be fixed until the bug # 6353 is fixed.

Mobile processes document check-in, and check-out in batches of 75 documents.  While checking in your documents, if you cancel the check-in process, Mobile performs the usual end of batch process.  It then asks you if you want to delete the Mobile copies of the documents that you were checking in.  After you answer, Mobile asks you the same question once for each batch remaining to be processed, only if you had more than 75 documents being checked in.  For example, if you are checking in 750 documents and you cancel out of the check-in  process during the first batch, Mobile asks you if you want to delete the Mobile copies 10 times, once for each batch of 75 documents.  Although you can exit out by closing down the Mobile database, we do not recommend it.  We recommend that you answer the question(s) each time until Mobile is finished with the check-in process.

- Was trying to download the document types to the MOBILE library.  When he clicks on  - download a window telling him that the download is taking place pops up briefly and then disappears.

Install/TBLCOMP.EXE

6383 - Tblcomp automatically defaults the dll name when you choose tcp/ip no matter what else may have been in the connect string in the win.ini file. The connect string in the win.ini file says: PCNFS=WDBSUNTC,128.223.2.240,1507,urgent.  WDBSUNTC was the dll She gave me to run PC-NFS attaching to Sun/Sybase using the Generic Network Driver.  However, because the dll name is not one which tblcomp recognizes, it defaults to network type of "other" and deletes the port information on the tblcomp connect screen (see the attached ole bitmap for more information).  When you click on tcp/ip to make the port number field available, tblcomp changes the name of the dll to WDBNOVTC.  It also changes the value in the win.ini file.  tblcomp should recognize that just because you are using tcp/ip to connect doesn't mean you are using Novell's tcp/ip and thus doesn't mean you are using wdbnovtc.dll.

ADDLIB.EXE

5884 - Sometimes, when addlib is setting up remote libraries, it says 'Could not setup remote libraries'.  When you look, they're set up, but either one is repeated in the 'change library' list, or there is a blank in the 'change library' list. 

Known Issues in DOCSOPEN for DOS

DOCSOPEN for DOS Desktop

6340 - LEGAL industries SYBASE databases on NOVELL networks.  Problem Printing a document and creating new documents

5179 - DEFAULT industries SYBASE databases on NOVELL networks.  Program will GP if tester cancels out of the Hit List box from the Quick Retrieve menu.  

5234 - LEGAL industries SYBASE databases on NOVELL networks. Getting a copy of a document when your not suppose to.  

5306 - SYBASE databases on NOVELL networks.  Saving to remote libraries.

5307 - LEGAL industries SYBASE databases on NOVELL networks.  Updating the quick retrieve box at the remote library.

5308 - LEGAL industries SYBASE databases on NOVELL networks.  Error logs for Checking out, deleting, and coping documents. 

6331 - All industries SYBASE databases on NOVELL networks. Deleting from Profile Search Hit List does not remove profile immediately. 

7113 - LEGAL industries SYBASE databases on NOVELL networks.  Checkout file should be del when checked in.

6391 - All industries SYBASE databases on NOVELL networks.  Update to doc name from display/ed it profile is not reflected in Quick Retrieve until exit and re-enter.

6399 - All industries SYBASE databases on NOVELL networks.  Profile Search , return from no document profiles found is incorrect. 

6558 - All industries SYBASE databases on NOVELL networks.  Use Template screen, problem with Enter = Cancel and an invalid message.  

6420 - All industries SYBASE databases on NOVELL networks.  Profile Search on dates using minus command doesn't work. 

6421 - All industries SYBASE databases on NOVELL networks.  Number of Items found does not equal number of items on a hit list.

6485 - All industries SYBASE databases on NOVELL networks.  "Shadowed copy newer..." message is missing 2 lines.  

6536 - All industries SYBASE databases on NOVELL networks.  View document after full text search - hits are not highlighted.

6549 - All industries SYBASE databases on NOVELL networks.  DOS Client User's Guide missing instructions.

6694 - All industries SYBASE databases on NOVELL  networks.  You must hit the Alt-S twice to do a Table look-up search.  

5102 - DEFAULT industries SYBASE databases on NOVELL networks.  Performing searches from the Quick Retrieve and Profile Search screen while in document  #2.  

5600 - LEGAL industries SYBASE databases on NOVELL40 networks.  If you delete a document it will show up on the profile search and the quick retrieve but if you try to view the profile or launch the file it will tell you that doesn't exist.  But when you exit out it will not show up.  

3965 - LEGAL industries SYBASE databases on NOVELL networks.  If you try to retrieve a SECURED document on a document server that you are NOT attached to,  the program should display a LOGIN form to get username and password and then attempt to login to that document server.  

5135 - DEFAULT industries SYBASE databases on NOVELL networks.  Typing time is incorrect when retrieving a document into a newly created document. 

6973 - All industries All databases on All networks.  PCDOCS should only list functioning command line parameters. 

4103 - DEFAULT industries SYBASE databases on NOVELL   networks.  Double clicking on an item in a lookup (like client or matter) should place it in the profile field. 

Library Maintenance

4582 - All industries All databases on NOVELL40 networks.  Inability to see Network Servers....  in Library  Maintenance... 



