Hi,I’ve am attempting to add a new column to an existing view using the CAPI.
I started out using the following CAPI eample programs
notesapi\samples\dbdesign\makeview
notesapi\samples\dbdesign\readview
These give you a good idea of the basic structure such a CAPI program should have.
I have hit a road block arounf the format of the $VIEWFORMAT structure.
It is documents as follows:
The structure of this data is as follows:
[ VIEW_FORMAT_HEADER ]
[ VIEW_TABLE_FORMAT ]
[ VIEW_COLUMN_FORMAT #0 ] n columns, as specified in VIEW_TABLE_FORMAT.
[ VIEW_COLUMN_FORMAT #1 ]
...
[ VIEW_COLUMN_FORMAT #n ]
[ COLUMN DATA #0 ] n columns, as specified in VIEW_TABLE_FORMAT.
[ COLUMN DATA #1 ]
...
[ COLUMN DATA #n ]
[VIEW_TABLE_FORMAT2]
[ VIEW_COLUMN_FORMAT2 #0 ] n columns, as specified in VIEW_TABLE_FORMAT.
[ VIEW_COLUMN_FORMAT2 #1 ]
...
[ VIEW_COLUMN_FORMAT2 #n ]
[ VIEW_TABLE_FORMAT3 ]
I’m struggling to find documentation around what follows the VIEW_TABLE_FORMAT3 structure.
Has anyone got experience of writing such a program, I’s be very greatful of any advice/documentation/samples available
Subject: RE: Using CAPI to add new columns to a view
Hi,
I posted a PMR to IBM a couple of months ago regarding this. Even tough they DO mention view_table_format4/5 and view_column_format3/4/5 (and a very interesting but very missing file called “viewprops.h”) they won’t reveal how it all fits together. If you look at the view (created with later versions of Notes) there are quite a lot of data that comes after view_column_format3 (things that relates to SameTime awareness , CDRESOURCE structures, etc).
One learns to recognize bits and pieces of signatures by just looking at hex-dumps but the real problem is knowing how it all fits together.
The only thing i could find out was that they could not reveal any more since that would mean that they also had to publish quite a lot of other proprietary stuff (and by a lot they did mean A LOT).
I guess one way is to (when reading) treat the stuff after view_table_format3 as a “blob”.