Overview of Smart Components

---

Since version 7.0, Pervasive.SQL has offered a component architecture called Smart Components, which improves installation and run-time reliability and makes application troubleshooting easier.

In earlier Pervasive Software releases, some developers experienced one or more of the following problems:

• Installation of a new application (with old client Requester components) overwrote new Requester components in shared locations, causing old applications to fail the next time they ran.
• Installation of a new Workgroup engine was incompatible with existing client Requesters. Existing client Requesters loaded the old engine, failing to provide features required by the new application.
• Difficulty identifying the function, version, and patch level of installed components.
• Difficulty determining the root cause of run-time operational failures, especially in client/server operation.

The Smart Components architecture is designed to reduce or eliminate these problems by providing the following features and benefits:

• Component Identification: Component function, major, and minor functional level are easily identified to aid in problem resolution.
• Unique Component Naming: Each release of a given component has a unique file name, so that updated versions of a component never overwrite previous versions. A Pervasive upgrade will not damage existing Pervasive-based applications.
• Dynamic Binding: Pervasive.SQL no longer loads a fixed set of program files into memory. Dependent components are loaded only if another component specifically requires its functionality, major, and minor functional level. Incompatible components are never accidentally loaded, reducing or eliminating version-related failures.
• Pervasive.SQL Event Logging: All components report errors and messages to a central log, easing the burden of troubleshooting.
• Error Code Clarification: Error conditions from underlying layers are logged through to the Pervasive.SQL Event Log, rather than hidden within an umbrella status code. Because the root causes of certain errors can now be more quickly determined, troubleshooting is much easier.