Conference abbott::teamlinks_windows

TWo things, put INFOMAN in the CFCLOGOPTIONS line. This might give us an 
idea where it's hanging,.

Second why do they have a Teamlinks association for Word? What happens when 
they get rid of the association?

MIke

Did they install ODMA?

Today I just found a new problem with Word 97 and I wonder if
they have run into it.  It appears that MS Office 97 updates
the Reg.dat with the entries that make TL Infoman do an ODMA
style launch for all Word file types.  On Windows NT, TL 2.7
does not install the 32-bit ODMA pieces.  (If you select to
install ODMA on WinNT, TL only installs its 16-bit pieces.)  
So the launch of the Word 97 does not work, because there is
no ODMA32 and TLODMA32 for it to connect to.  The error
message shows the ODMA DocID, which begins with 
"::ODMA\TEAMLNKS\...".

The work around is to remove the ODMA32.FileTypes entries in 
Reg.dat for Word's three file types.  Then Infoman will do a 
regular launch of Word using a filespec in the command line.

It's interesting that MS did this only for Word 97 file types,
not for PowerPoint and Binder.  I still have to verify this
on another PC.  They didn't tell me they were going to define
these Reg.dat entries.  If they had I might have caught this
before 2.7 shipped.  Heavy sigh...

This same situation could occur on Windows 95 if the user
does not install TeamLinks ODMA support.  That's easy to do
since it isn't installed by default.  For now the work-around
on Windows 95 is to either install ODMA support or delete
the ODMA32.FileTypes entries for Word in Reg.dat as described
above.

I will see about fixing this at least in TL 3.0 EFT2 and maybe
in an ECO to 2.7 if possible.

Can the customer check this?

Bob

Debbie,

About the new problem I entered in the .2 reply.  Most likely that
is not the problem.

I re-installed Word 97 on another PC and Word did not make the
ODMA32.FileTypes entries in Reg.dat as I had feared.  I also
verified this on Jerry's and Don's PCs.  They can launch WINWORD6 
files and TL does a regular launch, not an ODMA launch.  So it
was a false alarm.  I would have received lots of bug reports from
Word 97 users if it had been the case, especially from WinNT users.

I must have caused those Reg.dat entries to be created somehow on
my WinNT PC.  But I don't know how.

It's still something that TL should check for.  I'll try to make
TL more bulletproof in this area in 3.0 EFT2.  If any ODMA files or
Reg.dat entries are missing, then TL won't do an ODMA launch.

So your customer has a different problem.  We've had some problems
with 32-bit apps installed in directories that have long filenames.
(Mike just fixed it in TL 3.0.)  Is that the case here?

Also, like Mike asked, is it really necessary for them to have that 
TL File Association for Word?  They should remove it to see if the 
problem goes away.

Bob

    Bob, Mike, anyone,
    
    I talked with the customer with the intent of asking about ODMA, etc.
    They did not install ODMA by the way.  They did have more interesting
    information for me, however.  They said the more they played around
    the stranger the problem has gotten.
    
    1. They have MailWorks for VMS as their server and they are
       set up for both DECnet and IP.  On the IP side they have 
       some servers with TGV multinet and UCX.
    
    2. This problem appears to happen only on PC's they have never
       had a previous version of TeamLinks or Office and are new
       Windows 95 installs.
    
    3. The problem does NOT appear to happen with DECnet as their
       transport.
    
    4. It did not happen with UCX in our test.  It does happen
       with TGV multinet BUT some TGV multinet users are fine
       some are not.  It only happens with OFFICE97 documents
       not on Lotus AmiPro or other applications.
    
    They had to sign off for the evening so we will continue to work
    tomorrow.
    
    Debbie Giannetti

Debbie,
	Until we get a log file there's not much else we can do. A copy of 
their office.ini would also help. What version of Multinet are they using?
Do any of their users have Office95?

Mike  

    I talked with the customer this morning.  Further investigation has
    revealed detailed behavior.
    
    The customer received a message from his boss that had been sent to
    a distribution list of 9 people.  He (the customer I was talking to)
    was one of the recipients as well as his coworker that sits next to
    him.  He was using NT 4.0 with TeamLinks 2.7-1 and his coworker was
    using NT 3.51 with TeamLinks 2.5-4.
    
    When he read the message and replied he only received 2 recipients
    instead of the 9.  This was from the NT4.0 and TeamLinks 2.7-1.
    
    When the coworker read and attempted to reply they received all the
    recipients. This was from the 2.5-4 and NT 3.51.
    
    He switched VMS (MailWorks) accounts from the PC's and the problem
    followed the account.  I had him go into x4man and remove the user
    and add them back in - made no difference.
    
    I didn't see any profile fields that were obvious that could affect
    this behavior.
    
    Any idea?
    
    Debbie Giannetti

Is this a new problem, but same customer? Sounds
like this behavior would be unrelated to launching
Office97 apps.

I don't know offhand if the problem with recipient
is known or if it has been fixed. Perhaps someone
else will chime in.

Jerry

    Jerry,
    
    Please ignore .6 (momentary lapse of reasoning)
    
    Debbie Giannetti

I'll have to take back all those nice comments I
made regarding the CSC folks in ALF. You'd never
catch engineering making mistkeas ni thsi ntoesflile.

;^)

Jerry