Title: | TeamLinks for Windows |
Notice: | Kit and ECO locations: See replies to note 8. o note 8. |
Moderator: | ORION::chayna.zko.dec.com::tamara::eppes AN |
Created: | Mon Aug 28 1995 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 2238 |
Total number of notes: | 9650 |
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1926.1 | Lets grasp a few straws | XANADU::draft.zko.dec.com::xanadu::lawrence | TeamLinks Engineering, DTN 381-0747 | Thu Jan 30 1997 10:54 | 10 |
Could you have them try it again with trace on. I can't think of any reason why this shouldn't work and I have not heard this problem before. Additionally could we get a copy of office.ini, autoexec.bat and a look at the teamlinks directory. Is it possible that there is more than 1 tladdr.dll on the system? Cheers, jal | |||||
1926.2 | going to backup resolved issue | OASS::ANDRES_B | Thu Jan 30 1997 14:29 | 9 | |
Well I called the customer back to have them turn on trace and get the files. He said they restored the PC from a backup on tape and he thinks it was upgraded to 2.7 and the error is not occuring now. I have no idea was solved this but it is now solved. Thanks, Beth |