Your life will be easier if you call
jr_context.set_workarea( &your_workarea_name );
before you start looking at the ci_* tables. That will make only one
version of each object visible at a time. I'm not familiar with the PK
and PK items parts off the top of my head so I can't directly answer
your problem, but this may help.
Open the design editor, find a PK, hit F4 to open the properties
palette, then hit F5. You'll get a dialog box that tells you the table
and irid for that item. It also has buttons to open up MODEL and API
help. You'll want model, which will open an html document describing
your ci_* table as well as any links to it or from it. I'd expect
primary keys to have a link from ci_columns.
andrewst wrote:
> Originally posted by Iain Brown
>
>
>>Hi,
>
>
>
>>I've been given the lovely task of documenting the contents of my
>>project's
>
>
>>database tables.
>
>
>
>>I got told to use report generator with the ci_ views, e.g.
>
>
>>ci_table_definition, ci_primary_key_constraints... etc.
>
>
>
>>Anyway, I managed to get what I needed for the table itself, but
>>for the key
>
>
>>constraints, I cannot find how the ci_ views link the keys to
>>their fields.
>
>
>>E.g. a primary key called 'MME_PRK' was made up of 3 fields. Yet the
>
>
>>ci_primary_key_constraints view contained 10 records with the name
>>MME_PRK',
>
>
>>all identical except the IVID and PARENT_IVID fields - which are
>>the version
Received on Fri Aug 29 2003 - 17:59:57 CDT
