diff -r 43e37759235e -r 51a74ef9ed63 Symbian3/SDK/Source/GUID-9665C072-EA52-54B8-87A3-A7F818940DCD.dita --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Symbian3/SDK/Source/GUID-9665C072-EA52-54B8-87A3-A7F818940DCD.dita Wed Mar 31 11:11:55 2010 +0100 @@ -0,0 +1,39 @@ + + + + + +What +is the CommsDat APIThis topic is an intrdouction to the CommsDat API. Tools and applications +use the CommsDat API to access the data in the Comms Database. +

The CommsDat DLL implements the CommsDat API. Symbian platform +loads the CommsDat DLL at boot time. Tools and applications do not load the +DLL.

+

The API made available by the CommsDat DLL is the only method that users +can use to access the data in the Comms Database. The API maps between client-side +representations of the data and the data stored in the database.

+

Tools and applications see the data as a set of tables. A table is a set +of records, where each record is an ordered set of fields. Each field holds +a specified piece of information. A field at a given position in a record +contains the same type of data in all records. You can consider that each +field at a given location in a record is in a column. A table can also be +called a record set.

+ + + +

Tables, records, columns and fields are all CommsDat elements. An element +is an item that can be stored in the Comms Database.

+

The CommsDat API gives tools and applications a set of classes to retrieve, +create and change the elements in the Comms Database. The API also gives the +functionality to access the Comms Database.

+

+
+How is the + Comms Database secured +
\ No newline at end of file