FutureWare’s Application Security Object provides a convenient and centralized means of controlling user access to applications’ features and functionalities for all Borland development tools that support the TComponent object and its descendents. Each application can have multiple security profiles (e.g., full rights, read-only, etc), each made from the associated forms’ control objects that are controlled using four levels of presentation management: No Change, Disabled, Enabled, and Hidden. Application users are assigned security profiles and are validated when they open an application using their network ID, but they can also be validated by other authentication methods. When the user successfully opens an application, their assigned profile is dynamically built by the security object for all forms and components available to the user during their working session. The FutureWare Application Security Object, part of the FutureWare's FrameWork III development environment, uses ADO for the data access methods, and is designed for Delphi 5 and 6, C++Builder and Kylix.

The Application Security Object consists of three elements: The security object proper, typically created and used during the application’s MainForm OnCreate event when validating the user’s logon credentials A database object that contains the secured applications, users and associated security profiles A management utility program, used to create the security profiles, user lists and application information. The utility itself can be included within an application for “super users”. The FutureWare Application Security Object is available in three versions: Stand-alone, using MS Access Thin-client client/server, using MS Access, MS SQL or Oracle Thin-client n-Tier for MS SQL or Oracle, using MIDAS in one of three configurations: Socket Server DCOM CORBA

The FutureWare Application Security Object's Development Utility program, used to create and manage the secured applications, users, and profiles