Conference abbott::teamlinks_windows

Hello Andrew

I think what your asking is to convert a Word document to Wordperfect and
that is possible with TeamLinks. The customer my however to save space not have
installed all the converters so they may have to go back to install/customize
and install the converters they require.

Rick

All the other apps you mention have their own capabilities to convert
files.  For example Ami Pro can open Word 2.0 files.  WordPerfect 6.1 
can open Word 6/95 files.  Like TL, you have to see what converters
these apps have and which the users have installed.  Sometimes they
call them filters.

You might be able to find one format and version that all the apps
can read.

Bob

Rick/Bob,

I thought about the converters installed and as I didn't do the original 
install. As such, I went back to re-install. I'm pretty sure I selected all 
the converters. I will however check.

Keep in mind that the "sender" sits on a PC with only Word and TeamLinks. 
That's it. He/she sends to a machine in another network with only Word Perfect 
 and TeamLinks. 

I realize that the other "receiving" PC's may have various applications 
converter inherent within. The need however is to SEND the document 
preformatted rather than have the recipient decode/convert it.

This brings me back to the original question, how do you do this. Lets forget 
T/L for the moment and assume all we have installed is Word. If I do a Save AS 
I get the option of one of many file types to choose, of which WP is one. This 
no longer seem to be an option once T/L was installed. 

Either way, I will re-verify the converters installed on the client. Any other 
thoughts?

					/ Andrew /

Andrew,

>This brings me back to the original question, how do you do this. Lets forget 
>T/L for the moment and assume all we have installed is Word. If I do a Save AS 
>I get the option of one of many file types to choose, of which WP is one. This 
>no longer seem to be an option once T/L was installed.

I might be wrong, but the TL integration for Word 95 should allow
you to do a File Save As to the FC in WP format if the WP converters
in Word has been installed.  It has nothing to do with the converters
in TL that were installed.  The Save As to DOS should have whatever
converters were installed when installing Word 95.

Bob

OK, here's the poop.

Microsoft Word v7.0 (Office 95)
I have verified that all converters are loaded

Teamlinks 2.7
I have verified (and reinstalled) the converters and viewers.

1) If I bring up Word, create file and do Save As.
	- I get prompted for destination folder
	- Select MS-DOS
	- Select Save As Type
	   and get a very large selection, including WP.

	Good. Even works.

2) If I bring up Word, create file and do Save As.
	- I get prompted for destination folder
	- Select folder and click Options... button
	- I am prompted with the choice of 7 file type options.
	    the general DOS,Text,RTF type stuff.

	Very Bad.

	One might think this is a T/L problem

3) If I bring up Word, create file and do Save As.
	- I get prompted for destination folder
	- Pick folder and accept default Word doc type.
	- Bring up T/L.
	- Access folder where saved file exists.
	- Select file
	- Use pull-down menus File->Convert...
		and get a very large selection, including WP.

	Good. Even Works.

	This implies T/L converters are there.


So.....

If I save to DOS, life is rosey. This kinda defeats the purpose of T/L though.

If I first save the doc as word then go into T/L, convert the file and then 
send it, it works. This is too many steps.

Option 2 above is the 'reasonable' solution you would expect.
	create doc
	send doc as file type <blah>

Should one be able to do this?? If so, any other pointers as to why this isn't 
working would be very well received. The customers whole T/L 
strategy/investment is centered around whether or not they can do option 2.

Thanks in advance for any insight.
						/ Andrew /
						NSIS Toronto, Canada

Andrew,

Your right.  The list displayed by the Word 7.0 TL integration is limited.

This is not the case with the TL integration for Word 6.0.  Extensive
work was done in that application to properly detect all converters
installed.  It looks like either that work was not brought over into
the Word 7.0 integration or Word 7.0 stores this information differently
than Word 6.0.  Word 6.0 puts this in INI files and Word 7.0 puts it
into the Windows Registry.  They are 2 different apps with 2 different
TL integrations.

Al Poon is going to look at this to see if there's any work-around
you can use to make TL detect the WP converter in Word 7.0.

Bob