| Ivan,
A few questions:
1. Are these drawers local drawers stored on a network (Pathworks) drive?
2. What are the exact steps to reproduce the problem? For example:
- Invoke Ami Pro from Windows, or File.New from Infoman?
- File Open File Cabinet Document
- Select a (template?) document from read only (local?) drawer
- Click Insert
- File Create File Cabinet Document
- Specify a document to create in the non read only drawer
- Error occurs here?
- Help About - Update TeamLinks Connections
- File Create File Cabinet Document again
- Specify a document to create in the non read only drawer
- This time it works?
3. Whatever the steps are, could you provide a CFCDEBUG.LOG? Set logging in
office.ini as follows:
[TeamLinks]
CFCLOGOPTIONS=NEWLOG LOG FILECAB
4. Why didn't they update to TeamLinks 2.7 instead of 2.5? I don't know if this
problem would be fixed in 2.7, but that is the most recent version.
5. Once you get the exact steps from the customer, can you try to reproduce it
also?
Thanks,
John
|
| I have requested that the customer create the Trace log, though in the
mean time, the procedure he follows is as below. (I am trying to set
the similar environment up myself for testing purposes).
Teamlinks Infoman - File New
AMIPRO - File New
Select a Style sheet
Enter some data.
File Open and Insert the Read only text from a Network drive.
Save file to a network drive which user has full access to.
Error ocurrs at this point.
Help About Teamlinks Integration - Update File Cabinets..
Save again without problem.
Unfortunately the customer has had to do so many changes, a Teamlinks
upgrade is not likely for a while. (Government customers take an age
to get anything authorised). Though it has been recommended.
I will post the Trace log later, and also when/if I mange to duplicate
the problem, I post any results.
Many Thanks
Ivan.
|
| Ivan,
Please be sure of the exact menu commands that are executed.
Is it File Open, or File Cabinet Open Document - DOS button?
Is it File Save, or File Cabinet Create Document - DOS button?
Here is how I tried to reproduce the problem. I have 2 network drives,
one is read/write (I:) and one is read only (Q:).
1. Infoman File New, select AMI PRO document. Ami Pro comes up. Ami Pro
caption says: Ami Pro - [INFOMAN: New FC Document]
2. File New, select "default.sty". Ami Pro caption changes to:
Ami Pro - [Untitled].
3. Type some text.
4. File Open, select a text file on drive Q: and click the Insert button.
The text is inserted.
5. File Save. Ami Pro "Save As" dialog comes up. I specify I:\JUNK\FOO.SAM
and click Enter. No error occurs, and the file is created.
If I instead try to save to the read only drive (Q), I get an Ami Pro error:
Cannot write to directory Q:\.....
(rather than the TeamLinks Integration error you referred to in .0).
If all you do is File Open, File Save, etc., it does not make sense that
you would get a "TeamLinks Integration" error, since no attempts to
access the TeamLinks file cabinet have been made yet.
Let me know if you can get this to happen on your system (using 2.5, 2.7, 3.0?)
That will make it easier for us to track this down. My testing has been done
using TeamLinks 3.0 on Windows 95 and Windows 3.11, with network drives on VMS
systems.
Did you say the customer's were on a Unix system? I wonder if they could
reproduce the problem on a VMS network drive.
If you have access to a 2.5 system, it would be interesting to see if you
can reproduce it on 2.5 or 2.7 (or 3.0 if you have it). I don't think anything
in the TeamLinks Ami Pro integration has changed between 2.7 (or even 2.5) and
3.0 that would affect this behaviour, but it's hard to be sure. 2.5 is pretty
old at this point.
Thanks,
John
> I have requested that the customer create the Trace log, though in the
> mean time, the procedure he follows is as below. (I am trying to set
> the similar environment up myself for testing purposes).
>
> Teamlinks Infoman - File New
> AMIPRO - File New
> Select a Style sheet
> Enter some data.
> File Open and Insert the Read only text from a Network drive.
> Save file to a network drive which user has full access to.
> Error ocurrs at this point.
> Help About Teamlinks Integration - Update File Cabinets..
> Save again without problem.
>
> Unfortunately the customer has had to do so many changes, a Teamlinks
> upgrade is not likely for a while. (Government customers take an age
> to get anything authorised). Though it has been recommended.
>
> I will post the Trace log later, and also when/if I mange to duplicate
> the problem, I post any results.
>
> Many Thanks
> Ivan.
|
| Thanks for trying this out for me, I have managed to setup two file
services from a Unix system running Pathworks, and cannot reproduce the
error. I was using TL2.7 I will now try a 2.5 configuration. Sorry if
this is a red herring, but I havent been able to get the relevant
software to try this out.
Ivan
|