[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
|
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
2148.0. "Wrong doc returned after GOLD-I, left RESERVED" by COMICS::BARHAM (Norbert:) Mon Jan 25 1993 10:52
ALL-IN-1 3.0
This is a very reproducable problem that severely impacts the customers new
customisation. His problems are that the document returned in the current item
block after doccreate is not always the one he expects to be there. Also
the document that should have been returned is left in a RESERVED state so
users can't edit it.
e.g. Create a new document in a shared drawer.
While in the editor, Gold-I, SP, File to MAIN drawer. You get an error like
"Problem with COPY function - file [.DOC9]ZUNDF04GE.WPL"
Gold-w
%OA-I-CAB_CANT_FIND, The current File Cabinet document cannot be found
%OA-E-NOCOPY, Problem with COPY function - file "[.DOC9]ZUNDF04GE.WPL"
-OA-E-TXTOPNERR, TEXT DSAB open error
%OA-I-LASTLINE, Document created <-- ** It has in docdb but no file created
Press F10 (exit Scratch Pad Editor Menu)
Press F10 (return to editor)
Press F10 (save doc)
The document in the current item block has changed to the one you named in the
'Creating from Scratch Pad' form. When you try and read it, it says
'This file does not exist'.
Now select the shared drawer again.
The document here is the one we expected to see but it is in a RESERVED state
so other users cannot access it.
This scenario, and possibly others that don't return the right document to
the current item block, severly impacts their application.
I have been unable to tell him his customisation issue is consultancy since
he produced this example and he is after a high level escalation asap. He needs
to know why the document returned is not the one that he started creating so
that he might have a chance of trapping it or working around it. Also why is
it left RESERVED ?
Thanks for any input.
Clive Barham
UK CSC
T.R | Title | User | Personal Name | Date | Lines |
---|
2148.1 | Clarification request | IOSG::MAURICE | Because of the architect the building fell down | Mon Jan 25 1993 11:23 | 14 |
| Hi,
The root problem, I think, is that WPS-PLUS cannot be invoked twice.
You can simplify your problem by creating a document in the MAIN drawer
and repeating the Scratch Pad test - i.e. you don't need shared drawers
to get the problem.
Is this the problem with your customer's customisation - i.e. does
your customer need the ability to create two WPS-PLUS documents
simultaneously?
Cheers
Stuart
|
2148.2 | | COMICS::BARHAM | Norbert: | Mon Jan 25 1993 14:23 | 7 |
| Thanks for the quick response Stuart. It seems that the main reason for
using GOLD-I while editing is to read new mail. Whatever the reason,
sometimes the edited document gets stuck in a RESERVED status.
Thanks
CLive
|
2148.3 | There are two problems | IOSG::NEWLAND | Richard Newland, IOSG, REO2-G/L2 | Mon Jan 25 1993 15:46 | 23 |
| There are two problems:
1. The SP F option calls a script (OA$LIB:SPFILE). This script was not
modified during the development of V3.0, and therefore was not updated to
handle drawers. It does not save and restore the drawer context if the
file operation is done to a different drawer. Please submit an SPR to
report this.
2. If you are using the WPS-PLUS editor and do GOLD-I, SP F to create a
WPS-PLUS document you hit the other problem you described. This is caused
by the WPS-PLUS editor opening the WPSDEF.WPL file for exclusive write
access which prevents the WPS-PLUS text dataset also opening WPSDEF.WPL to
get your default print settings.
There is a workaround which is to create an ASCII document by pressing NEXT
SCREEN on the Create Document form and setting the Handling to "ASCII EDT".
The contents of the Scratch Pad are saved in an ASCII text file so you
won't lose any document attributes.
Richard
|