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 |
TeamLinks 2.7 ECO1 Windows 95 Windows NT 4.0 Novell WordPerfect 6.1 with the TLODMA Customer has TeamLinks 2.7 and has installed ECO1. She previously had TeamLinks 2.5-4. They use WordPerfect and using ODMA they were able to perform a Merge with 2.5-4 that they now cannot do with TeamLinks 2.7 ECO1. The steps are as follows: From WordPerfect Tools Merge Form A window appears with "Create Merge File" in the title bar The options are... _ Use file in Active Window OK _ New Document Window CANCEL HELP Selects OK with the "Use file in Active Window" chosen Select the Associated Data file from the TeamLinks File Cabinet A window appears with "Create Form File" in title bar _ Associate Date File ::odma\teamlnks\#local\[my OK _ None CANCEL HELP Specify the data file that goes with the form file you are creating, or choose None for No association Now Selects the "Associate Data File" with the document name in the ::odma\teamlinks.... string OK WPWin Error Non valid filename specified in ::odma\teamlnks\#local\[my%020local%020fc]kathy's%020local%020drawer OK The customer did not receive this error using 2.5-4 but now receives this error in 2.7 and 2.7 with ECO1. All other forms of using merge appear to work just fine. Any ideas?
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2036.1 | XANADU::cascobay.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Thu Mar 06 1997 17:06 | 20 | |
Are they sure they were using ODMA to integrate with WP 6.1 back when they were using TeamLinks 2.5-4? They only way could have done that was to manually install the files in the TLODMA25.ZIP file. Did they do that? The reason I ask is they might have been using the direct Filecab.dll integration. That might have worked. Did they add an ODMA updates from Novell or Corel into WordPerfect 6.1? They usually have names like ODMAR4.ZIP or ODMAR5.ZIP (which is the latest). They should be up to ODMAR5 by now. I think I know what the problem is. It looks like the ODMA Document ID string has been lowercased. This was a problem with some commands in WP. I thought they had fixed it but maybe not. We might need a PTR on this one. Bob | |||||
2036.2 | ODMA | AIMTEC::GIANNETTI_D | Mon Mar 10 1997 12:25 | 13 | |
Bob, I talked with the customer (City of Wichita, Cathy Westphal). She did in fact have the ODMA installed in 2.5-4 with WordPerfect 6.1. She procured it from you. She had the exerpt from the notesfile with instructions, etc. and the file it referred to was odmae.zip... She received it 12/26/95. Do I need to enter PTR? Thanks, Debbie Giannetti | |||||
2036.3 | XANADU::CUMMINGS | Jerry Cummings, TeamLinks | Mon Mar 10 1997 12:57 | 6 | |
Bob's in a class this week, so I don't know when he'll be responding. He has been known to wander through the notes file in the evening hours, so hopefully he'll respond soon. Jerry | |||||
2036.4 | Try Update 5. I'll remind Corel about this. | XANADU::flymht.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Tue Mar 11 1997 20:16 | 36 |
Hi Debbie, > I talked with the customer (City of Wichita, Cathy Westphal). She > did in fact have the ODMA installed in 2.5-4 with WordPerfect 6.1. > She procured it from you. She had the exerpt from the notesfile > with instructions, etc. and the file it referred to was odmae.zip... > She received it 12/26/95. Wow! This was a long time ago! It was 61ODMAE.ZIP and that was the first ODMA update to WP 6.1 from Novell. I think I remember talking to them. That update is pretty old and I never tested it against TL 2.7 or 2.7-001. Off hand I don't know why it wouldn't work. The ODMA code in TL 2.7 is a bit stricter and more robust. Also the Document ID was changed slightly to eliminate spaces and double-quote characters. I don't know why the newer ODMA code would effect this one mail merge function in WP 6.1 using Update 1. It's now Corel that owns WP. They are up to update 5 now. They've made quite a lot of changes to fix bugs and improve ODMA interaction. See FAQ topic 31.6. You might want to mail that note to them. Perhaps they can try update 5 on one PC to see if that helps with this problem. I did forward the text from the base topic to Corel. The person at Corel who handles this left me a voice mail message about this report the other day. He's a bit swamped and hasn't had a chance to look into it and respond. I'll try to remind him about this. I'm sure the first thing he will ask is that they try Update 5. So have the customer try it. I suspect it will not help, but who knows, maybe it will. Bob | |||||
2036.5 | Something to check, plus it would be nice to have a log file. | XANADU::flymht.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Tue Mar 11 1997 20:36 | 18 |
Hi again Debbie, Another thing to check. Is it possible that when this Mail Merge error occurs that the documents involved are in a TL 2.7 Local "internet" file cabinet and that TL is currently in Offline mode? If so, have them put TL back online or put the documents into a regular TL Local FC and try it again. There's a bug in this combination. I don't think that's the problem, but I'm just trying to cover all the bases. They could enable "LOG, FILECAB, TLODMA" logging in the CFCLOGOPTIONS key in Office.ini, then reproduce the problem and send the resulting CFCDEBUG.LOG file. It will prove to me if the bug is from Corel or Digital. Bob | |||||
2036.6 | Debug log file | ALFSS2::GIANNETTI_D | Fri Mar 28 1997 20:51 | 86 | |
**** CFC started Thu Mar 27 07:39:31 1997 **** CFCIOS DLL version: TeamLinks Client IOS BaseLevel BL61 ALL-IN-1 on node MONEY is version V3.1 with TLC V2.5, running File Cabinet Server version 4 AIDA DLL version: V3.2-0 AIDA$RG35B AIDA Server version on money: V2.5-1 AIDA$ICF038 TLODMA: ODMGetODMInterface (riid=0x0, ppvObj=0x4bbf032c, pUnkOuter=0x0, pReserved=0x0, lpszAppId=0x4bbf0306, dwEnvData=0x298) TLODMA: Input lpszAppId= "WordPerfect" Length=11 TLODMA: FilecabSessId=39162 TLODMA: AddRef Object=0x3dd702ee RefCount=2 TLODMA: Release Object=0x3dd702ee RefCount=1 TLODMA: Output *ppvObj= 0x3dd702ee TLODMA: HRESULT value from ODMGetODMInterface = 0x0 TLODMA: AddRef Object=0x3dd702ee RefCount=2 TLODMA: Release Object=0x3dd702ee RefCount=1 TLODMA: ODMGetDocInfo (lpszDocId=0x3d0f19a2, item=2 {ODM_NAME}, lpszData=0x354fdb34, dataLen=156) AppId="WordPerfect", FcSessId=39162 TLODMA: Input lpszDocId= "::ODMA\TEAMLNKS\#LOCAL\[MY%020LOCAL%020FC]Kathy's%020Local%020Drawer\3460300000000" Length=82 TLODMA: Output lpszData= "Conference call questions" Length=25 TLODMA: ODMNewDoc (lpszDocId=0x3d0f14be, dwFlags=0x10, lpszFormat=0x354fd55e, lpszDocLocation=0x0) AppId="WordPerfect", FcSessId=39162 TLODMA: Input lpszFormat= "WordPerfect 6.0/6.1 (*.wpd;*.wpt;*.doc;*.wp)" Length=44 TLODMA: Output lpszDocId= "::ODMA\TEAMLNKS\NEW1" Length=20 TLODMA: ODMSaveAs (lpszDocId=0x3d0f14be, lpszNewDocId=0x354fdbfa, lpszFormat=0x354fd4d8, pcbCallback=0x319f102a, pInstanceData=0x354fd514) AppId="WordPerfect", FcSessId=39162 TLODMA: Input lpszDocId= "::ODMA\TEAMLNKS\NEW1" Length=20 TLODMA: Input lpszFormat= "WordPerfect 6.0/6.1 (*.wpd;*.wpt;*.doc;*.wp)" Length=44 ALL-IN-1 on node MONEY is version V3.1 with TLC V2.5, running File Cabinet Server version 4 TLODMA: Output lpszNewDocId= "" Length=0 TLODMA: ODMGetLeadMoniker (lpszDocId=0x3d0f14be, ppMoniker=0x354fd60e) AppId="WordPerfect", FcSessId=39162 TLODMA: Input lpszDocId= "::ODMA\TEAMLNKS\NEW1" Length=20 TLODMA: ODMSTATUS = 1 (ODM_E_FAIL) TLODMA: ODMGetDocInfo (lpszDocId=0x3d0f14be, item=2 {ODM_NAME}, lpszData=0x354fd57e, dataLen=128) AppId="WordPerfect", FcSessId=39162 TLODMA: Input lpszDocId= "::ODMA\TEAMLNKS\NEW1" Length=20 TLODMA: Output lpszData= "DATA DOC" Length=8 TLODMA: ODMOpenDoc (flags=0x11, lpszDocId=0x354fd442, lpszDocLocation=0x354fd0a2) AppId="WordPerfect", FcSessId=39162 TLODMA: Input lpszDocId= "::ODMA\TEAMLNKS\NEW1" Length=20 TLODMA: Output lpszDocLocation= "C:\TEAMLINK\STAGING\FC000542.WPD" Length=32 TLODMA: ODMSaveDoc (lpszDocId=0x354fd442, lpszNewDocId=0x3d0f14be) AppId="WordPerfect", FcSessId=39162 TLODMA: Input lpszDocId= "::ODMA\TEAMLNKS\NEW1" Length=20 TLODMA: Output lpszNewDocId= "::ODMA\TEAMLNKS\#LOCAL\[MY%020LOCAL%020FC]Kathy's%020Local%020Drawer\3490300000000" Length=82 TLODMA: ODMGetDocInfo (lpszDocId=0x354fdbfa, item=2 {ODM_NAME}, lpszData=0x354fd566, dataLen=156) AppId="WordPerfect", FcSessId=39162 TLODMA: Input lpszDocId= "::ODMA\TEAMLNKS\#LOCAL\[MY%020LOCAL%020FC]Kathy's%020Local%020Drawer\3490300000000" Length=82 TLODMA: Output lpszData= "DATA DOC" Length=8 TLODMA: ODMGetDocInfo (lpszDocId=0x354fd506, item=4 {ODM_TITLETEXT}, lpszData=0x354fd506, dataLen=156) AppId="WordPerfect", FcSessId=39162 TLODMA: Input lpszDocId= "::ODMA\TEAMLNKS\#LOCAL\[MY%020LOCAL%020FC]Kathy's%020Local%020Drawer\3490300000000" Length=82 TLODMA: Output lpszData= "DATA DOC" Length=8 TLODMA: ODMSelectDoc (lpszDocId=0x49af1976, pdwFlags=0x354fd802) AppId="WordPerfect", FcSessId=39162 TLODMA: Input *pdwFlags=0x0 TLODMA: Output *pdwFlags=0x1 TLODMA: Output lpszDocId= "::ODMA\TEAMLNKS\#LOCAL\[MY%020LOCAL%020FC]Kathy's%020Local%020Drawer\3490300000000" Length=82 TLODMA: ODMGetODMInterface (riid=0x0, ppvObj=0x4bbf0342, pUnkOuter=0x0, pReserved=0x0, lpszAppId=0x4bbf0306, dwEnvData=0x298) TLODMA: Input lpszAppId= "WordPerfect" Length=11 TLODMA: FilecabSessId=39166 TLODMA: AddRef Object=0x3dd71460 RefCount=2 TLODMA: Release Object=0x3dd71460 RefCount=1 TLODMA: Output *ppvObj= 0x3dd71460 TLODMA: HRESULT value from ODMGetODMInterface = 0x0 TLODMA: AddRef Object=0x3dd71460 RefCount=2 TLODMA: Release Object=0x3dd71460 RefCount=1 TLODMA: ODMGetDocInfo (lpszDocId=0x354fd7a6, item=3 {ODM_TYPE}, lpszData=0x49af1df6, dataLen=156) AppId="WordPerfect", FcSessId=39166 TLODMA: Input lpszDocId= "::odma\teamlnks\#local\[my%020local%020fc]kathy's%020local%020drawer\3490300000000" Length=82 TLODMA: ODMSTATUS = 11 (ODM_E_DOCID) DDE command: [read_new_mail] DDE command: [read_new_mail] CFCIOS reverting to slow list (61/34) DDE command: [read_new_mail] | |||||
2036.7 | XANADU::cascobay.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Tue Apr 01 1997 19:41 | 19 | |
Thanks for the log Debbie. Sorry it took me so long to get back in this notes conference. I think there are 2 problems at play here. It's beens so long since I've seen the ODMA code for TL 2.5, but I have a feeling it wasn't quite so strict as the 2.7 code. WP is lowercasing the DocID string, which is wrong, and TL 2.5 may have let it get away with it. Was this mail merge only working with local FC documents under TL 2.5? Did they ever try it with ALL-IN-1 documents? The reason I ask is I think the Local FC can tolerate its DocID being lowercased, but I know that ALL-IN-1 FS server cannot. I will look into this ASAP to if I can make a work-around. But we still need Corel to fix it. Bob | |||||
2036.8 | Something for the customer to try. | XANADU::cascobay.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Mon Apr 07 1997 15:12 | 17 |
Debbie, I tested it and I think I've come up with a work-around, at least for WP merge documents in a TL Local FC. I made the TL ODMA code allow ODMA DocIDs to be lowercased. It doesn't mean the will always work, but at least TL will not reject them so easy. The updated DLLs are here: xanadu::user06:[stjean.public]wpmerge.zip There's a readme.txt file in there that tells what to do. Get this to the customer and have them test it out. Let me know if it works. Bob | |||||
2036.9 | XANADU::flymht.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Wed Apr 09 1997 15:43 | 5 | |
Debbie, Did the customer try this out yet? Bob | |||||
2036.10 | I'll let you know about this one | AIMTEC::GIANNETTI_D | Tue Apr 22 1997 13:02 | 7 | |
Bob, I'm getting to the customer now. I have been working on the call in the first half of my open list. Now I'm getting to the back of the list. I'll let you know. Debbie Giannetti |