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

Conference iosg::all-in-1

Title:	ALL-IN-1 (tm) Support Conference
Notice:	Please spell ALL-IN-1 correctly - all CAPITALS!
Moderator:	IOSG::PYECE

Created:	Fri Jul 01 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2716
Total number of notes:	12169

2627.0. "Adding an addressee field to the Index form" by KERNEL::SIMPSONR (fred) Wed Apr 16 1997 21:01

ALL-IN-1 V3.1

Hi just a quick question. The customer has basically added an additional search
field which was addressee onto the ALL-IN-1 Index option. It only finds the
first addressee rather than whole lot when searching a distribution list. Has
anyone written any code to provide this functionality?

Cheers,
Richard Simpson.

T.R Title User Personal
Name Date Lines

2627.1 Will imapct performance and is not trivial IOSG::MARSHALL Thu Apr 17 1997 18:56 26

T.R	Title	User	Personal Name	Date	Lines
2627.1	Will imapct performance and is not trivial	IOSG::MARSHALL		`Thu Apr 17 1997 18:56`	26
	First, you don't want to use addressees on an index form. Addressees are stored in the document attribtues file (DAF) which, while allowing a rich set of attributes/structure to be stored does not have the efficiency of direct keyed retrieval that you get with DOCDB. All the fields that ALL-IN-1 uses on index forms come from DOCDB. To start using DAF attributes on indexes would have a serious impact on performance. You can't add addressees to the DOCDB, as they're a repeatable attribute and the DOCDB only supports one occurence of an attribute (which is why its retrieval time is quicker). However, if you still want to persist with this: CAB$ is the main file cabinet dataset. It provides a unified interface to both the DOCDB and DAF files. However, to do this it only supports one occurence of the repeated DAF attribute. Hence you only 'see' the first addressee on a message when using CAB$. You need to use the 'extended' dataset CAB$ATTRIBUTES to access the repeated DAF attributes. In your case, you'd have to have an outer loop that selected every document in turn, then used CAB$ATTRIBUTES to see if that document contained an addressee you were interested in, and if it did add the document to your index. All I can say to that is, good luck! :-) Scott

First, you don't want to use addressees on an index form.  Addressees are stored
in the document attribtues file (DAF) which, while allowing a rich set of
attributes/structure to be stored does not have the efficiency of direct keyed
retrieval that you get with DOCDB.

All the fields that ALL-IN-1 uses on index forms come from DOCDB.  To start
using DAF attributes on indexes would have a serious impact on performance.  You
can't add addressees to the DOCDB, as they're a repeatable attribute and the
DOCDB only supports one occurence of an attribute (which is why its retrieval
time is quicker).

However, if you still want to persist with this:

CAB$ is the main file cabinet dataset.  It provides a unified interface to both
the DOCDB and DAF files.  However, to do this it only supports one occurence of
the repeated DAF attribute.  Hence you only 'see' the first addressee on a
message when using CAB$.  You need to use the 'extended' dataset CAB$ATTRIBUTES
to access the repeated DAF attributes.

In your case, you'd have to have an outer loop that selected every document in
turn, then used CAB$ATTRIBUTES to see if that document contained an addressee
you were interested in, and if it did add the document to your index.

All I can say to that is, good luck! :-)

Scott