Current recordset does not support updating
The logical data model of the database is independent of the eventual target database (Oracle/SQL Server.) The logical schema is exposed as a normalized, in-memory representation of data.
The logical schema is similar to the physical schema, but does contain some differences.
This enables a developer to build and distribute a client/server application without targeting a specific DBMS.
In cases where special business functions need to be exposed via the ODBC interface, stored procedures are used to allow the client to invoke functions not directly related to data manipulation.
When clients want to see project level details, they must increment the scope_level for those projects from 1 to 7.
The Primavera SDK does not, however, support more than one connection to a Primavera SDK data source on any given client machine.
A client program using the Primavera SDK driver participates in the same concurrency mechanism as other Project Management client programs.
For example, calculated fields such as Earned Value may be included in the logical schema, but they are not stored directly in the physical schema.
These fields are calculated in memory and are accessible via the Primavera SDK.
Other applications are notified of changes made via the Primavera SDK driver, and the Primavera SDK is able to detect when changes are made to the underlying data by other applications.