Passwording different modules within a project

[RIJ]

Is it possible to place different passwords on different modules within a project??

RIJ

 

[Foada]

I am not sure of exactly what you are asking, nor have I tried it but I suppose you could prevent the addition of an object of a Class module by utilizing a password. Can you provide any details? If you choose to battle wits with the witless be prepared to lose.

 

[RIJ]

We have a Eord VBA Form which opens an Access DB and puts data from it into bookmarks in the Word Form, and we have a bunch on standard routines which does a lot of the repatitous stuff - and want to be able to put different passwords on the main VBA and the 'common routines' - all in the same project.

Make sense?

 

[Foada]

I am half way there, what modules are you refering to in place different passwords on different modules? What are you looking to do, anything like this:

..
..
..
If sUserPassword = "goodpass" Then
...do this
else
MsgBox "Wrong Password"
End If
..
..
Am I on the right track? If you choose to battle wits with the witless be prepared to lose.

 

[MichaelRed]

Also, what secutity processing are you doing?

Then again, USERS shouldn't be looking at code in VB, so the 'better' approach might be to just put the code in a dll, and / or compile the prog to native code. Not many left around to figure that out - even if they can 'see' it.

MichaelRed
m.red@att.net

There is never time to do it right but there is always time to do it over

 

[RIJ]

Ah!
That might be the answer. Is there a basic guide to making a DLL about?

The situation i have is that we have one 'smart client' who knows our main p/w but either way, proberly entitled to it as he paid for the VBA(!!) but i want to make it hard for him to create/change stuff by 'claiming' the code in the 'common routines' (which make our life much much easier when generating new code) we have written. Its to do with revenue protection.

So, if i can find out about making a DLL or making something to add under 'References', then i am to some degree, protected...i think..

 

[MichaelRed]

I'm pretty sure were not communicating vere clearly. Thsi is a VISUAL BASIC Forum. You seem to be discussing Visual Basic APPLICATIONS[\b] commonly referred to as VBA. Both VB and Ms. A. use both forms and "visual basic", - however there ARE significant differences - particularrly w/ respect to security. In Ms. A, there is a built in security system which includes MANY different properties or levels of security for different objects and for different users and groups (of users). In this environment, you can set up various objects to be available to different users / groups at very precise levels. Unfortunately, SOMEONE (or several SOMEONES) must have the 'right' to ever object in design mode - or no maintenance can be accomplished.

POVB on the otherhand is normally distributed as a COMPILED program, and access to the design is grenerally available only to those who actually have the source seperatly.

Both can make use of DLL's, however with POVB it is not uncommon to include them just to make code management easier. With Ms. A, my only experience with them is -like your situation- just to keep code from 'prying eyes'.

In either case, you need to be very careful about implementing code (or even objects) in dll's as you can easily run afoul of contract language. If, for indtance, your contract says that all development under the contract is deliverble to the client in source form, and you include any procedure in a dll, you are responsible for the delivery of the source code foru the entire dll to that customer. This MAY necessitate the 'delivery' of code developed for a different contract which just happend to bundeled into the sae dll. It needs a legal begal to keep all of it straight.

MichaelRed
m.red@att.net

There is never time to do it right but there is always time to do it over