[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::teamlinks_windows

Title:TeamLinks for Windows
Notice:Kit and ECO locations: See replies to note 8.o note 8.
Moderator:ORION::chayna.zko.dec.com::tamara::eppesAN
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

2198.0. "keyword length shorter in 2.7 than in 2.1" by BACHUS::COLLART (Li p'ti fouineu - Dtn 856-8796) Tue May 13 1997 20:12


			Hello,




	A customer will upgrade from Teamlinks for Windows 2.1-006
	to Teamlinks 2.7 and they are facing some problems.

	The keyword field allow a lot more information in 2.1 than in 2.7

	Alcatel Belgium was using this keywords to allow easy search
	in their ISO9000 document procedures but the keyword field is
	truncated to 50 characters after upgrade to Teamlinks 2.7

	It is a serious problem for them and Alcatel wants I open an IPMT
	severity 2 for that.

	I made some tests and I even see nothing kept in the keyword if
	it was a single string of characters (without space) longer than
	50 characters (my string was > 256 characters)

	Is there a way to save the defined keywords while upgrading
	from 2.1 to 2.7 ?
	Is this change/limitation/bug/feature documented somewhere ?

	I know 50 characters is what is available within an ALL-IN-1 drawer
	and I saw this lentgh limit also in some characteristics of FCLIST.

	Last note, the document are kept in local drawers.



						Thanks for help

						Eric Collart
						MCS Brussels
T.RTitleUserPersonal
Name
DateLines
2198.12.1 to 2.7 is a bit jump! Keyword processing got tighter.XANADU::cascobay.zko.dec.com::TAMARA::STJEANBob St.JeanTue May 13 1997 23:0023
Somewhere along the line the CFC_Keywords attribute was made
into a multivalue attribute.  I don't know which version that
happened in.  Also the CfcQueryAttributeSupport function eventually
became fully supported by all the CFC file cabinet types.  This
allowed the UIs in Filecab.dll, Fclist.dll, Infoman.exe and some
other places to ask the file cabinet if they support Keywords
and what the max keyword size is.

There is a problem in that Infoman uses spaces to delimit
keywords.  I think the Filecab.dll dialogs and API use both
commas and spaces.  I think only commas should be used.

What dialog box does this problem happen in?  There are lots of
places that allow Keywords to be set or changed.  The Save As
in integrated apps, the Import dialog, the File Attributes dialog,
and perhaps others...

ALL-IN-1 definitely has a limit of 50 characters for the keywords.
I think the Local FC has a limit of 256 characters, but perhaps
Dave Rought can verify this.

Bob

2198.2I will check which dialogBACHUS::DBC026::brssws::collartLi P'ti FouineuWed May 14 1997 11:4715


		Hello Bob,



	Thanks for quick answer...

	I don't in which dialog customer checked this,
	I will ask and come back...



				Eric
2198.3From File attribute in InfomanBACHUS::COLLARTLi p'ti fouineu - Dtn 856-8796Wed May 21 1997 08:1516
		Hello,


	here is the answer from customer:



When trying to change/add the keywords thru selecting a document in the
filecabinets and selecting File, Attributes from the menu.



					Thanks for help

					Eric
2198.4We found it!XANADU::cascobay.zko.dec.com::TAMARA::STJEANBob St.JeanWed May 21 1997 21:3724
Dave Rought and I both independantly tested this.  Yes you are
right, it is limiting the user to only 50 characters for the
Keywords attribute.  It's happening on the Save As and File
Attributes dialogs.

This used to work, but somewhere along the line it was broken.
The TL Local FC does not impose any limit to the length of the
Keywords attribute, so Filecab.dll imposes a limit of 300
characters.

The problem is that CFCLOCAL.DLL has put two Keywords elements
into an array that FILECAB.DLL reads.  The first occurance says 
there is no limit (0) then a later element says there is a 50 
character limit.  So FILECAB is using the later value of 50.  It
only needs one element for Keywords.  We don't know why this 
extra one is in there.

We'll look into fixing CFCLOCAL.DLL.  Thanks for reporting this.

If/when we fix this will the customer be able to live with a 300
character limit for Keywords in the TL Local FC?

Bob

2198.5Good, answer for to-morrowBACHUS::COLLARTLi p'ti fouineu - Dtn 856-8796Thu May 22 1997 07:1022
		Hello,

>
>If/when we fix this will the customer be able to live with a 300
>character limit for Keywords in the TL Local FC?
>


	I will ask to customer. Another point is customer will probably
	wants to fix this for 2.7 (cust will deploy X2.7, it is Alcatel).

	In this case, I suppose you need I open an IPMT case.

	I have an account meeting with customer this afternoon, I should
	be able to answer you to-morrow.


					Thanks for support

					Eric Collart
					MCS Brussels
2198.6OK for 300 characters in 2.7BACHUS::COLLARTLi p'ti fouineu - Dtn 856-8796Fri May 30 1997 08:1418

			Hello,


	Sorry for the long delay to answer (my fault)....


	Yes, customer will be happy with a field lentgh of 300 characters !

	Any chance it will come in ECO 3 ?

	Do you need an IPMT case to justify ?

					Thanks for support

					Eric Collart
					MCS Brussels
2198.7Fixed in V3.0 and ECO 3XANADU::x400it.zko.dec.com::xanadu::roughtThu Jun 05 1997 20:294
The Keyword restriction of 50 characters will be fixed in V3.0 and
V2.7-ECO3.

					Dave