![]() ![]() ![]() ![]() |
| Topics this page:
|
|
To call COM from .NET: To expose .NET components to COM (unmanaged code): Universal Data Access (UDA) was Microsoft's ambitious vision that "Any client should be able to use data regardless of where and how it is stored. Conversely, any computer that stores data should be capable of sharing that data with any client." The technical term for this is "heterogeneous data access." To obtain information from a database on a server, programmers need to first connect to a data source on a server, then specify parameters to issue commands for retrieving a recordset containing fields . The (Microsoft® Data Access Components) MDAC SDK provides the infrastructure to implement Microsoft's COM (Component Object Model) architecture of components. ODBC 1.5x first appeared December 1997. MDAC 2.0 was released in July '98 with the introduction of Visual Studio 6. MDAC 3.5 arrived April, 1993. Microsoft (Open DataBase Connectivity) ODBC Driver Manager library (odbc32.dll) manages communication between applications and ODBC drivers. ODBC drivers are available for every major DBMS in use today, including non-Microsoft database products such as Oracle and Sybase as well as for Microsoft's SQL Server, FoxPro®, and Access. Data Access Objects (DAO) provide native COM interfaces (object models) to Microsoft's JET (Joint Engine Technology) database engine shipped with Access and Visual Basic. Jet is really a series of .DLL files that manage data access. JET is based on the Index Sequential Access Method (ISAM) which works with simple flat structured indexes.
Perl 5 programmers use the Database Independent Interface (DBI) module. Remote Data Objects (RDO) provides a COM interface overlay to ODBC API since the Enterprise Edition of Visual Basic 5.0. DAO and RDO were phased out by Microsoft. DAO allows databases to be encrpyted using DES. Using DAO and Jet you can create groups of users that have various priviliges. You can set passwords as well. I have developed financial apps using DAO and Jet that have multi-tiered security profiles. [Thus,] some users could do things that others could not. These capabilities are built-in to DAO/Jet. ADO is a generalized approach to many data stores. |   |
|
|
| ![]() ![]() ![]() |
| ![]() ![]() ![]() |
| ![]() ![]() ![]() |
|
| ![]() ![]() ![]() |
| JDK 1.2 IDL
| ![]() ![]() ![]() |
|
| ![]() ![]() ![]() |
Here is a sample script generated by VuGen against a login to the sample COM flight application:
| ![]() ![]() ![]() |
|
Aspect | Metric | Description | Notes |
---|---|---|---|
Authentication | Authenticate | Frequency of successful method call level authentication. When you set an authentication level for an application, you determine what degree of authentication is performed when clients call into the application. | |
Authenticate Failed | Frequency of failed method call level authentication. | ||
Application Events | Activation | Frequency of application activation or startup. | |
Shutdown | Frequency of application shutdown or termination. | ||
Thread Events | Thread Start | Rate at which single-threaded apartment (STA) thread for application have been started. | |
Thread Terminate | Rate at which single-threaded apartment (STA) thread for application have been terminated. | ||
Work Enque | Event sent if a work is queued in single thread apartment object (STA). Note: These events are not signaled/sent in Windows Server 2003 and later. | ||
Work Reject | Event sent if a work is rejected from single thread apartment object (STA). Note: These events are not signaled/sent in Windows Server 2003 and later. | ||
Transaction Events | Transaction Duration | Duration of COM+ transactions for selected application. | |
Transaction Start | Rate at which transactions have started. | ||
Transaction Prepared | Rate at which transactions have completed the prepare phase of the two-phase protocol. | ||
Transaction Aborted | Rate at which transactions have been aborted. | ||
Transaction Commit | Rate at which transactions have completed the commit protocol. | ||
Object Events | Object Life Time | Duration of object existence (from instantiation to destruction). | |
Object Create | Rate at which new instances of this object are created. | ||
Object Destroy | Rate at which instances of the object are destroyed. | ||
Object Activate | Rate of retrieving instances of a new JIT-activated object. | ||
Object Deactivation | Rate of freeing JIT-activated object via SetComplete or SetAbort. | ||
Disable Commit | Rate of client calls to DisableCommit on a context. DisableCommit declares that the object's transactional updates are inconsistent and can't be committed in their present state. | ||
Enable Commit | Rate of client calls to EnableCommit on a context. EnableCommit declares that the current object's work is not necessarily finished, but that its transactional updates are consistent and could be committed in their present form. | ||
Set Complete | Rate of client calls to SetComplete on a context. SetComplete declares that the transaction in which the object is executing can be committed, and that the object should be deactivated on returning from the currently executing method call. | ||
Set Abort | Rate of client calls to SetAbort on a context. SetAbort declares that the transaction in which the object is executing must be aborted, and that the object should be deactivated on returning from the currently executing method call. | ||
Method Events | Method Duration | Average duration of method. | |
Method Frequency | Frequency of method invocation. | ||
Method Failed | Frequency of failed methods (i.e. methods that return error HRESULT codes). | ||
Method Exceptions | Frequency of exceptions thrown by selected method. |
If you want to display more than 20 of these counters, see Mercury problem ID 26871 to change the ini file.
Related:
![]()
| Your first name: Your family name: Your location (city, country): Your Email address: |
Top of Page ![]() Thank you! |