T.R | Title | User | Personal Name | Date | Lines |
---|
2198.1 | 2.1 to 2.7 is a bit jump! Keyword processing got tighter. | XANADU::cascobay.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Tue May 13 1997 20:00 | 23 |
| 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.2 | I will check which dialog | BACHUS::DBC026::brssws::collart | Li P'ti Fouineu | Wed May 14 1997 08:47 | 15 |
|
Hello Bob,
Thanks for quick answer...
I don't in which dialog customer checked this,
I will ask and come back...
Eric
|
2198.3 | From File attribute in Infoman | BACHUS::COLLART | Li p'ti fouineu - Dtn 856-8796 | Wed May 21 1997 05:15 | 16 |
|
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.4 | We found it! | XANADU::cascobay.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Wed May 21 1997 18:37 | 24 |
| 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.5 | Good, answer for to-morrow | BACHUS::COLLART | Li p'ti fouineu - Dtn 856-8796 | Thu May 22 1997 04:10 | 22 |
|
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.6 | OK for 300 characters in 2.7 | BACHUS::COLLART | Li p'ti fouineu - Dtn 856-8796 | Fri May 30 1997 05:14 | 18 |
|
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.7 | Fixed in V3.0 and ECO 3 | XANADU::x400it.zko.dec.com::xanadu::rought | | Thu Jun 05 1997 17:29 | 4 |
| The Keyword restriction of 50 characters will be fixed in V3.0 and
V2.7-ECO3.
Dave
|