| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2010.1 | | XANADU::CUMMINGS | Jerry Cummings, TeamLinks | Tue Feb 25 1997 09:19 | 10 |
| Office 97 is not yet supported. There's a note in this
conference (maybe in the FAQ notes) about what works,
what doesn't, what can sort of work, etc.
The launch problem will be fixed in V3. The workaround
you discovered is what we do, or sometimes we simply
have the required app running before launching the
attachment. That seems to work too.
Jerry
|
| 2010.2 | NT 4.0 is not 16 bit friendly | TAMARA::laceup.zko.dec.com::tamara::fitzell | It's not a bug it's functionally challenged ! | Tue Feb 25 1997 10:43 | 36 |
| >Would the above change in the registry be enough to use TeamLinks 2.7-1
>with Word 97 or should all 'Winword.exe' entries be changed?
Yes changing the registry entry to short names will work. The only other
entry you may want to change is the \shell\print.
>Will this problem be addressed soon in a fix or ECO for TeamLinks V2.7-1?
>If Yes, is there an approximate date when the fix will be available?
>Customer plans to have his 200 TeamLinks clients upgraded to Office 97 in
>March
This is being fixed in V3.0. (EFT1 sometime the beginning of MARCH, SSB mid
summer) As of now it is not being considered for an ECO. NT 4.0 has a couple
of bugs in it's 16 bit support which is breaking our launch code; our fix is
quite extensive and I doubt we could do the necessary level of testing needed
in an ECO. Not having to muck with registry entries made it into the EFT1
code base; tracking 32 bit apps is still under developement.
>Are there any other points to be considered when using Office 97 with
>TeamLinks under Windows NT?
You will lose the TeamLinks integration, the launch tracking can easily get
confused which can lead to annoying/confusing messages and if you're sharing
documents and the launch tracking is confused you can lose data.
>Do we officially support now Office 97 under Windows NT 4.0 with TeamLinks
>Mail V2.7-1 or should the customer wait for a certain ECO to be officially
>supported
For 2.7-X it's no as to when it'll depend on what you mean by "Officially
supported". If you mean the application is integrated with Teamlinks then we
won't officialy support it until TeamLinks is a 32 bit app which isn't until
V4.0. If you mean being able to launch a DOC from TeamLinks make changes and
get those changes back into the File Cabinet then yes in V3.0.
Mike
|
| 2010.3 | It's a lot of work to support a new app suite the way our customers expect it. | XANADU::cascobay.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Fri Feb 28 1997 10:50 | 22 |
| Supporting a new app or app suite implies a lot for TeamLinks. We need
tags, bitmaps, viewers, sniffers, converters, printing, launching, file
cabinet integration (ODMA), mail integration (SMAPI), documentation and
online help. In some cases the servers need to know about the new file
types in order to handle them properly. It's nice if it works on all
platforms, and in some cases we can't do that on Windows NT.
A big issue for MS Office 97 is sniffer/converter/viewer support. We
don't know when we'll get that support from Mastersoft.
Our Windows NT limitations are pretty well documented in this notes
conference (i.e. ODMA & SMAPI). We're working on it. Mike explained
the launching differences.
There's a lot of QA and interoperability testing involved.
So a lot has to fall into place for us to "offically support" a new
app or app suite.
Bob
|