Hi i need some guideliness from u guys,

See i have created one project, it contained lot of sub modules...,

Take example, i created one ERP package...,

In that HR, Payroll, Filemanagement like this sub modules will be there...,

This all the things, i have in one project and the dll file name is project name...,

Now my question is, i like to differentiate the modules...,

It mean, while accesing my project "Enduser" will interacting with that one dll file...,

Suppose lot of enduser will interact this one dll, then it will be critical, then the process will be slow down...,

So i like to create each module as separate , separate dll's...,

so when the user interact with dll using his "Id" and "pwd", if he have to rights to access another dll, he can access else he wont disturb that dll...,

Example the enduser can have rights only HR and Payroll then he can interact with that 2 dll's only...,

So it will avoid enduser to access all the dll's & we can make process spead also high...,

How to procedure this?,

I dont have any team members with me,I am building this project alone,

So i like to share with u guys how to solve this probs...,

Enduser accessing that single dll using his id and pwd, now i want the above format,

For that what i have to do?, and how to achieve this one?,

Help me,

ManickMagesh:

so when the user interact with dll using his "Id" and "pwd", if he have to rights to access another dll, he can access else he wont disturb that dll...,

Example the enduser can have rights only HR and Payroll then he can interact with that 2 dll's only...,

One approach is use the RPC DCOM. You can access a COM component via DCOM and multiple users provide the authentication credentials to launch/access the component.

If user has been granted permission, he/she can run the dll success, else still get "access denied" errors.

For more information about DCOM technic, please view this article,

http://msdn2.microsoft.com/en-us/library/ms809332.aspx