File: ref.hyperwave.html

package info (click to toggle)
php3 3%3A3.0.18-0potato1.1
links: PTS
area: main
in suites: potato
size: 17,736 kB
ctags: 11,198
sloc: ansic: 108,120; sh: 2,512; php: 2,024; yacc: 1,887; makefile: 1,038; perl: 537; pascal: 238; awk: 90; cpp: 28; sql: 11
file content (942 lines) | stat: -rw-r--r-- 23,231 bytes
parent folder | download | duplicates (3)
<HTML
><HEAD
><TITLE
>Hyperwave functions</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"><LINK
REL="HOME"
TITLE="PHP Manual"
HREF="manual.html"><LINK
REL="UP"
TITLE="Function Reference"
HREF="funcref.html"><LINK
REL="PREVIOUS"
TITLE="setcookie"
HREF="function.setcookie.html"><LINK
REL="NEXT"
TITLE="hw_Array2Objrec"
HREF="function.hw-array2objrec.html"><META
NAME="HTTP_EQUIV"
CONTENT="text/html; charset=ISO-8859-1"></HEAD
><BODY
CLASS="reference"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>PHP Manual</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="function.setcookie.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="function.hw-array2objrec.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="reference"
><A
NAME="ref.hyperwave"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
>XXVI. Hyperwave functions</H1
><DIV
CLASS="PARTINTRO"
><A
NAME="AEN13274"
></A
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="hw-intro"
>Introduction</A
></H1
><P
>&#13;     <SPAN
CLASS="productname"
>Hyperwave</SPAN
> has been developed at <A
HREF="http://iicm.edu/"
TARGET="_top"
>IICM</A
> in Graz. It started with
     the name <SPAN
CLASS="acronym"
>Hyper-G</SPAN
> and changed to Hyperwave when
     it was commercialised (If I remember properly it was in 1996).</P
><P
>&#13;     Hyperwave is not free software. The current version, 4.1, is
     available at <A
HREF="http://www.hyperwave.com/"
TARGET="_top"
>www.hyperwave.com</A
>.  
     A time limited version can be ordered for free (30 days).</P
><P
>&#13;     Hyperwave is an information system similar to a database
     (<SPAN
CLASS="acronym"
>HIS</SPAN
>, Hyperwave Information Server). Its focus
     is the storage and management of documents. A document can be any
     possible piece of data that may as well be stored in file. Each
     document is accompanied by its object record. The object record
     contains meta data for the document. The meta data is a list of
     attributes which can be extended by the user. Certain attributes
     are always set by the Hyperwave server, other may be modified by
     the user. An attribute is a name/value pair of the form name=value.
     The complete object record contains as many of those pairs as the
     user likes. The name of an attribute does not have to be unique,
     e.g. a title may appear several times within an object record.
     This makes sense if you want to specify a title in several languages.
     In such a case there is a convention, that each title value is
     preceded by the two letter language abbreviation followed by a colon,
     e.g. 'en:Title in English' or 'ge:Titel in deutsch'. Other attributes
     like a description or keywords are potential candidates. You may
     also replace the language abbreviation by any other string as long
     as it separated by colon from the rest of the attribute value.</P
><P
>&#13;     Each object record has native a string representation with each
     name/value
     pair separated by a newline. The Hyperwave extension also knows
     a second representation which is an associated array with the
     attribute name being the key. Multilingual attribute values itself
     form another associated array with the key being the language
     abbreviation. Actually any multiple attribute forms an associated
     array with the string left to the colon in the attribute value
     being the key. (This is not fully implemented. Only the attributes
     Title, Description and Keyword are treated properly yet.)</P
><P
>&#13;     Besides the documents, all hyper links contained in a document
     are stored as object records as well. Hyper links which
     are in a document will be removed from it and stored as individual
     objects, when the document is inserted into the database.
     The object record of the link contains information
     about where it starts and where it ends.
     In order to gain the original document you will have
     to retrieve the plain document without the links and the list
     of links and reinsert them (The functions
     <A
HREF="function.hw-pipedocument.html"
><B
CLASS="function"
>hw_pipedocument()</B
></A
> and <A
HREF="function.hw-gettext.html"
><B
CLASS="function"
>hw_gettext()</B
></A
>
     do this for you. The advantage of separating links
     from the document is obvious. Once a document to which a link
     is pointing to changes its name, the link can easily be modified
     accordingly. The document containing the link is not affected
     at all. You may even add a link to a document without modifying
     the document itself.</P
><P
>&#13;     Saying that <A
HREF="function.hw-pipedocument.html"
><B
CLASS="function"
>hw_pipedocument()</B
></A
> and
     <A
HREF="function.hw-gettext.html"
><B
CLASS="function"
>hw_gettext()</B
></A
> do the link insertion automatically
     is not as simple as it sounds. Inserting links implies a certain
     hierarchy of the documents. On a web server this is given by the
     file system, but Hyperwave has its own hierarchy and names do not
     reflect the position of an object in that hierarchy. Therefore
     creation of links first of all requires a mapping from the Hyperwave
     hierarchy and namespace into a web hierarchy respective web namespace.
     The fundamental difference between Hyperwave and the web is the clear
     distinction between names and hierarchy in Hyperwave. The name does
     not contain any information about the objects position in the hierarchy.
     In the web the
     name also contains the information on where the object is located
     in the hierarchy. This leads to two possibles ways of mapping. Either
     the Hyperwave hierarchy and name of the Hyperwave object is reflected
     in the URL or the name only.
     To make things simple the second approach is used.
     Hyperwave object with name 'my_object' is mapped to
     'http://host/my_object' disregarding where it resides in the
     Hyperwave hierarchy.
     An object with name 'parent/my_object' could be the child of
     'my_object' in the Hyperwave hierarchy, though in a web namespace it
     appears to be just the opposite and the user might get confused. 
     This can only be prevented by selecting reasonable object names.</P
><P
>&#13;     Having made this decision a second problem arises. How do you
     involve PHP? The URL http://host/my_object will not call any
     PHP script unless you tell your web server to rewrite it to
     e.g. 'http://host/php3_script/my_object' and the script 'php3_script'
     evaluates the $PATH_INFO variable and retrieves the object with
     name 'my_object' from the Hyperwave server. Their is just one little
     drawback which can be fixed easily. Rewriting any URL would not allow
     any access to other document on the web server. A PHP script for
     searching in the Hyperwave server would be impossible. Therefore
     you will need at least a second rewriting rule to exclude certain
     URLS like all e.g. starting with http://host/Hyperwave. This is
     basically sharing of a namespace by the web and Hyperwave server.</P
><P
>&#13;     Based on the above mechanism links are insert into documents.</P
><P
>&#13;     It gets more complicated if PHP is not run as a server module or CGI
     script but as a standalone application e.g. to dump the content of
     the Hyperwave server on a CD-ROM. In such a case it makes sense to
     retain the Hyperwave hierarchy and map in onto the file system. This
     conflicts with the object names if they reflect its own hierarchy
     (e.g. by choosing names including '/'). Therefore '/' has to be
     replaced by another character, e.g. '_'. to be continued.</P
><P
>&#13;     The network protocol to communicate
     with the Hyperwave server is called <A
HREF="http://www.hyperwave.com/7.17-hg-prot"
TARGET="_top"
>HG-CSP</A
> 
		 (Hyper-G Client/Server Protocol). It is based on messages to initiate
     certain actions, e.g. get object record.  In early versions of
     the Hyperwave Server two native clients (Harmony, Amadeus) were
     provided for communication with the server. Those two disappeared
     when Hyperwave was commercialised.  As a replacement a so called
     wavemaster was provided. The wavemaster is like a protocol converter
     from <SPAN
CLASS="abbrev"
>HTTP</SPAN
> to <SPAN
CLASS="abbrev"
>HG-CSP</SPAN
>.  The idea is
     to do all the administration of the database and visualisation of
     documents by a web interface.  The wavemaster implements a set of
     placeholders for certain actions to customise the interface. This
     set of placeholders is called the <SPAN
CLASS="abbrev"
>PLACE</SPAN
> Language.
     <SPAN
CLASS="abbrev"
>PLACE</SPAN
> lacks a lot of features of a real programming
     language and any extension to it only enlarges the list of
     placeholders. This has led to the use of JavaScript which IMO does
     not make life easier.</P
><P
>&#13;     Adding Hyperwave support to PHP should fill in the gap of a
     missing programming language for interface customisation.  It
     implements all the messages as defined by the
     <SPAN
CLASS="abbrev"
>HG-CSP</SPAN
> but also provides more powerful commands
     to e.g. retrieve complete documents.</P
><P
>&#13;     Hyperwave has its own terminology to name certain pieces of
     information. This has widely been taken over and extended.
     Almost all functions operate on one of the following data types.

     <P
></P
><UL
><LI
><P
>&#13;	object ID: An unique integer value for each object in the
	Hyperwave server. It is also one of the attributes of the
	object record (ObjectID). Object ids are often used as an
	input parameter to specify an object.
       </P
></LI
><LI
><P
>&#13;	object record: A string with attribute-value pairs of the form
	attribute=value. The pairs are separated by a carriage return
	from each other. An object record can easily be converted into
	an object array with <B
CLASS="function"
>hw_object2array()</B
>.
	Several functions return object records.  The names of those
	functions end with obj.
       </P
></LI
><LI
><P
>&#13;	object array: An associated array with all attributes of an
	object. The key is the attribute name. If an attribute occurs
	more than once in an object record it will result in another
	indexed or associated array. Attributes which are language
	depended (like the title, keyword, description) will form an
	associated array with the key set to the language
	abbreviation. All other multiple attributes will form an
	indexed array. PHP functions never return object arrays.
       </P
></LI
><LI
><P
>&#13;	hw_document: This is a complete new data type which holds the
	actual document, e.g. HTML, PDF etc. It is somewhat optimised
	for HTML documents but may be used for any format.
       </P
></LI
></UL
></P
><P
>&#13;     Several functions which return an array of object records do also
     return an associated array with statistical information about
     them. The array is the last element of the object record
     array. The statistical array contains the following entries:
     <P
></P
><DIV
CLASS="variablelist"
><DL
><DT
>Hidden</DT
><DD
><P
>&#13;	 Number of object records with attribute PresentationHints
	 set to Hidden.</P
></DD
><DT
>CollectionHead</DT
><DD
><P
>&#13;	 Number of object records with attribute
	 PresentationHints set to CollectionHead.</P
></DD
><DT
>FullCollectionHead</DT
><DD
><P
>&#13;	 Number of object records with attribute
	 PresentationHints set to FullCollectionHead.</P
></DD
><DT
>CollectionHeadNr</DT
><DD
><P
>&#13;	 Index in array of object records with
	 attribute PresentationHints set to CollectionHead.</P
></DD
><DT
>FullCollectionHeadNr</DT
><DD
><P
>&#13;	 Index in array of object records with
	 attribute PresentationHints set to FullCollectionHead.</P
></DD
><DT
>Total</DT
><DD
><P
>&#13;	 Total: Number of object records.</P
></DD
></DL
></DIV
></P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="hw-apache"
>Integration with Apache</A
></H1
><P
>&#13;     The Hyperwave extension is best used when PHP is compiled as an
     Apache module. In such a case the underlying Hyperwave server can
     be hidden from users almost completely if Apache uses its rewriting
     engine. The following instructions will explain this.</P
><P
>&#13;     Since PHP with Hyperwave support built into Apache is intended
     to replace the native Hyperwave solution based on Wavemaster I
     will assume that the Apache server will only serve as a Hyperwave
     web interface. This is not necessary but it simplifies the
     configuration.  The concept is quite simple. First of all you
     need a PHP script which evaluates the <TT
CLASS="envar"
>PATH_INFO</TT
>
     variable and treats its value as the name of a Hyperwave
     object. Let's call this script 'Hyperwave'.  The URL <SPAN
CLASS="systemitem"
>http://your.hostname/Hyperwave/name_of_object</SPAN
>
     would than return the Hyperwave object with the name
     'name_of_object'. Depending on the type of the object the script
     has to react accordingly. If it is a collection, it will probably
     return a list of children. If it is a document it will return the
     mime type and the content. A slight improvement can be achieved
     if the Apache rewriting engine is used.  From the users point of
     view it would be more straight forward if the URL <SPAN
CLASS="systemitem"
>http://your.hostname/name_of_object</SPAN
> would
     return the object.  The rewriting rule is quite easy:

     <DIV
CLASS="informalexample"
><A
NAME="AEN13347"
></A
><P
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="programlisting"
>&#13;RewriteRule ^/(.*) /usr/local/apache/htdocs/HyperWave/$1 [L]
</PRE
></TD
></TR
></TABLE
><P
></P
></DIV
>

     Now every URL relates to an object in the Hyperwave server. This
     causes a simple to solve problem. There is no way to execute a
     different script, e.g. for searching, than the 'Hyperwave'
     script.  This can be fixed with another rewriting rule like the
     following:

     <DIV
CLASS="informalexample"
><A
NAME="AEN13349"
></A
><P
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="programlisting"
>&#13;RewriteRule ^/hw/(.*) /usr/local/apache/htdocs/hw/$1 [L]
</PRE
></TD
></TR
></TABLE
><P
></P
></DIV
>

     This will reserve the directory <TT
CLASS="filename"
>/usr/local/apache/htdocs/hw</TT
> for
     additional scripts and other files. Just make sure this rule is
     evaluated before the one above. There is just a little drawback:
     all Hyperwave objects whose name starts with 'hw/' will be
     shadowed. So, make sure you don't use such names. If you need
     more directories, e.g. for images just add more rules or place
     them all in one directory.  Finally, don't forget to turn on the
     rewriting engine with

     <DIV
CLASS="informalexample"
><A
NAME="AEN13352"
></A
><P
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="programlisting"
>&#13;RewriteEngine on
</PRE
></TD
></TR
></TABLE
><P
></P
></DIV
>

     My experiences have shown that you will need the following
     scripts:

     <P
></P
><UL
><LI
><P
>&#13;	to return the object itself</P
></LI
><LI
><P
>&#13;	to allow searching</P
></LI
><LI
><P
>&#13;	to identify yourself</P
></LI
><LI
><P
>&#13;	to set your profile</P
></LI
><LI
><P
>&#13;	one for each additional function like to show
	the object attributes, to show information about users,
	to show the status of the server, etc.</P
></LI
></UL
></P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="hw-todo"
>Todo</A
></H1
><P
>&#13;     There are still some things todo:
     <P
></P
><UL
><LI
><P
>The hw_InsertDocument has to be split into
	<B
CLASS="function"
>hw_InsertObject()</B
> and
	<B
CLASS="function"
>hw_PutDocument()</B
>.</P
></LI
><LI
><P
>The names of several functions are not fixed, yet.
       </P
></LI
><LI
><P
>Most functions require the current connection
	as its first parameter. This leads to a lot of typing, which
	is quite often not necessary if there is just one open
	connection. A default connection will
	improve this.</P
></LI
><LI
><P
>Conversion form object record into object array
        needs to handle any multiple attribute.
       </P
></LI
></UL
></P
></DIV
></DIV
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
><A
HREF="function.hw-array2objrec.html"
>hw_Array2Objrec</A
> &#8212; convert attributes from object array to object record</DT
><DT
><A
HREF="function.hw-children.html"
>hw_Children</A
> &#8212; object ids of children</DT
><DT
><A
HREF="function.hw-childrenobj.html"
>hw_ChildrenObj</A
> &#8212; object records of children</DT
><DT
><A
HREF="function.hw-close.html"
>hw_Close</A
> &#8212; closes the Hyperwave connection</DT
><DT
><A
HREF="function.hw-connect.html"
>hw_Connect</A
> &#8212; opens a connection</DT
><DT
><A
HREF="function.hw-cp.html"
>hw_Cp</A
> &#8212; copies objects</DT
><DT
><A
HREF="function.hw-deleteobject.html"
>hw_Deleteobject</A
> &#8212; deletes object</DT
><DT
><A
HREF="function.hw-docbyanchor.html"
>hw_DocByAnchor</A
> &#8212; object id object belonging to anchor</DT
><DT
><A
HREF="function.hw-docbyanchorobj.html"
>hw_DocByAnchorObj</A
> &#8212; object record object belonging to anchor</DT
><DT
><A
HREF="function.hw-documentattributes.html"
>hw_DocumentAttributes</A
> &#8212; object record of hw_document</DT
><DT
><A
HREF="function.hw-documentbodytag.html"
>hw_DocumentBodyTag</A
> &#8212; body tag of hw_document</DT
><DT
><A
HREF="function.hw-documentcontent.html"
>hw_DocumentContent</A
> &#8212; returns content of hw_document</DT
><DT
><A
HREF="function.hw-documentsetcontent.html"
>hw_DocumentSetContent</A
> &#8212; sets/replaces content of hw_document</DT
><DT
><A
HREF="function.hw-documentsize.html"
>hw_DocumentSize</A
> &#8212; size of hw_document</DT
><DT
><A
HREF="function.hw-errormsg.html"
>hw_ErrorMsg</A
> &#8212; returns error message</DT
><DT
><A
HREF="function.hw-edittext.html"
>hw_EditText</A
> &#8212; retrieve text document</DT
><DT
><A
HREF="function.hw-error.html"
>hw_Error</A
> &#8212; error number</DT
><DT
><A
HREF="function.hw-free-document.html"
>hw_Free_Document</A
> &#8212; frees hw_document</DT
><DT
><A
HREF="function.hw-getparents.html"
>hw_GetParents</A
> &#8212; object ids of parents</DT
><DT
><A
HREF="function.hw-getparentsobj.html"
>hw_GetParentsObj</A
> &#8212; object records of parents</DT
><DT
><A
HREF="function.hw-getchildcoll.html"
>hw_GetChildColl</A
> &#8212; object ids of child collections</DT
><DT
><A
HREF="function.hw-getchildcollobj.html"
>hw_GetChildCollObj</A
> &#8212; object records of child collections</DT
><DT
><A
HREF="function.hw-getremote.html"
>hw_GetRemote</A
> &#8212; Gets a remote document</DT
><DT
><A
HREF="function.hw-getremotechildren.html"
>hw_GetRemoteChildren</A
> &#8212; Gets children of remote document</DT
><DT
><A
HREF="function.hw-getsrcbydestobj.html"
>hw_GetSrcByDestObj</A
> &#8212; Returns anchors pointing at object</DT
><DT
><A
HREF="function.hw-getobject.html"
>hw_GetObject</A
> &#8212; object record</DT
><DT
><A
HREF="function.hw-getandlock.html"
>hw_GetAndLock</A
> &#8212; return bject record and lock object</DT
><DT
><A
HREF="function.hw-gettext.html"
>hw_GetText</A
> &#8212; retrieve text document</DT
><DT
><A
HREF="function.hw-getobjectbyquery.html"
>hw_GetObjectByQuery</A
> &#8212; search object</DT
><DT
><A
HREF="function.hw-getobjectbyqueryobj.html"
>hw_GetObjectByQueryObj</A
> &#8212; search object</DT
><DT
><A
HREF="function.hw-getobjectbyquerycoll.html"
>hw_GetObjectByQueryColl</A
> &#8212; search object in collection</DT
><DT
><A
HREF="function.hw-getobjectbyquerycollobj.html"
>hw_GetObjectByQueryCollObj</A
> &#8212; search object in collection</DT
><DT
><A
HREF="function.hw-getchilddoccoll.html"
>hw_GetChildDocColl</A
> &#8212; object ids of child documents of collection</DT
><DT
><A
HREF="function.hw-getchilddoccollobj.html"
>hw_GetChildDocCollObj</A
> &#8212; object records of child documents of collection</DT
><DT
><A
HREF="function.hw-getanchors.html"
>hw_GetAnchors</A
> &#8212; object ids of anchors of document</DT
><DT
><A
HREF="function.hw-getanchorsobj.html"
>hw_GetAnchorsObj</A
> &#8212; object records of anchors of document</DT
><DT
><A
HREF="function.hw-mv.html"
>hw_Mv</A
> &#8212; moves objects</DT
><DT
><A
HREF="function.hw-identify.html"
>hw_Identify</A
> &#8212; identifies as user</DT
><DT
><A
HREF="function.hw-incollections.html"
>hw_InCollections</A
> &#8212; check if object ids in collections</DT
><DT
><A
HREF="function.hw-info.html"
>hw_Info</A
> &#8212; info about connection</DT
><DT
><A
HREF="function.hw-inscoll.html"
>hw_InsColl</A
> &#8212; insert collection</DT
><DT
><A
HREF="function.hw-insdoc.html"
>hw_InsDoc</A
> &#8212; insert document</DT
><DT
><A
HREF="function.hw-insertdocument.html"
>hw_InsertDocument</A
> &#8212; upload any document</DT
><DT
><A
HREF="function.hw-insertobject.html"
>hw_InsertObject</A
> &#8212; inserts an object record</DT
><DT
><A
HREF="function.hw-mapid.html"
>hw_mapid</A
> &#8212; Maps global id on virtual local id</DT
><DT
><A
HREF="function.hw-modifyobject.html"
>hw_Modifyobject</A
> &#8212; modifies object record</DT
><DT
><A
HREF="function.hw-new-document.html"
>hw_New_Document</A
> &#8212; create new document</DT
><DT
><A
HREF="function.hw-objrec2array.html"
>hw_Objrec2Array</A
> &#8212; convert attributes from object record to object array</DT
><DT
><A
HREF="function.hw-outputdocument.html"
>hw_OutputDocument</A
> &#8212; prints hw_document</DT
><DT
><A
HREF="function.hw-pconnect.html"
>hw_pConnect</A
> &#8212; make a persistent database connection</DT
><DT
><A
HREF="function.hw-pipedocument.html"
>hw_PipeDocument</A
> &#8212; retrieve any document</DT
><DT
><A
HREF="function.hw-root.html"
>hw_Root</A
> &#8212; root object id</DT
><DT
><A
HREF="function.hw-unlock.html"
>hw_Unlock</A
> &#8212; unlock object</DT
><DT
><A
HREF="function.hw-who.html"
>hw_Who</A
> &#8212; List of currently logged in users</DT
><DT
><A
HREF="function.hw-getusername.html"
>hw_getusername</A
> &#8212; name of currently logged in user</DT
></DL
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="function.setcookie.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="manual.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="function.hw-array2objrec.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>setcookie</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="funcref.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>hw_Array2Objrec</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>