John, and others

This is a more complete description of my DCOM project.

It's a sequrity system that is implemented in DCOM way.

A client can register and unregister itself as a client for the security server. You must have the proper rights to do this (Administrator or something like that).

Once the client application is registered to the security server, The client application can asks the server if a user has access to a particular object.

Acceslevel:
0 - Not visible
1 - No access
2 - Readonly
3 - Full control

The object can be literally anything (A form, a menubar, a Commandbutton, a Page).

Within the server application, You can maintain users and usergroups, or link them to the domain-users and groups of the NT-server. Further you can grand users access to a particular object or object tree (An object can be a parent of other objects, like a directory structure) By setting permission to a parent object the childs automaticly inherit the persmissions, unless it is overruled on the child level.

Further you can monitor each user within a client application:
- Determine all active users
- Determine the historie of all started forms or other objects, started by a particular user.

Another feature is that it stores all errors that occured on the client apps. Giving you the ability to get statistical informaction about what problems do occur within the network.

WISH: The server application can be started from a client machine, using the same DCOM connection, so you can maintain the whole thing over a WAN connection.

Advantages:
- One server application controls all security of many client apps.
- The client app can be written in another language (VFP, VB, Access,... ??)
- Security of the server app and data is reached by using DCOM.

Walter,