Security and Protecting my work

[Crash1hd]

I created a big database program for a company. I want to protect it so that if any changes need to be made they have to either pay more or contact me to do so, I want to make it so that what they use is the user end version that is not editable or changeable but they can of course still use it! I tried to create a mde file but it says that its too big or something like that and wont create one I know that I can go into the startup and remove all the features but of course they can hold down the shift key and bypass that I also know that you can remove the feature for the shift key however here is my delema if I remove the bypass feature of the shift key then I wont be able to get into it to edit the forms when they do want me to upgrade it some one had mentioned a FE/BE type system but I was wondering how does that really work and if it slows down the program because its accessing another db file for the tables and do I put the queries in the FS or BS of the system? I am confused

I guess what I am wondering is what is the best method to protect my work?

P.S. I am also trying to figure out how I can make it shareware so that I can give them 90 days to try it then they have to pay for it to continue to use it. I figured I would create a form that says all of that with links on it that goto webpage and a buy button that grabs a product key in the vb code!

Thanks for any input!

 

[ghudson]

You should split your db into a front-end and back-end. It might be a little slower when you are accessing alot of records.

You should secure your db using the built-in Access security to create a workgroup(s) and passwords. You can then assign permissions to only the objects you want them to access.

You can also distribute the runtime version of Access but you will need to purchase the developers edition of Access.

Search the forum for you questions have been asked and answered before.

***Ensure that you fully understand how to secure you database before you actually try to do it and make copies of your database before and during your testing for you could lock yourself out of your database if you do not correctly secure it.

 

[Crash1hd]

I am not sure I understand the benifit of a FS / BS System? I mean wouldnt I have to secure both the front and back part of the system from getting access? Please explain!

You can also distribute the runtime version of Access but you will need to purchase the developers edition of Access

Where would that be if I had that version?

And I am very aware of backing up I have a macro setup so that everytime the user logs on or off there is a backup made, I was wondering is there a way in access to do a backup every couple of hours?

 

[ghudson]

My answer to using the Runtime was generic without getting into the details of using Access security [which is another story all by it's self].

You can easily test if a db was opened in the Runtime mode.

Public Sub Test()
    
    If (Not IsRuntime()) Then
        MsgBox "Not runtime", , "IsRuntime()"
    Else
        MsgBox "Is runtime", , "IsRuntime()"
    End If

End Sub

Function IsRuntime()
On Error GoTo Err_IsRuntime

    IsRuntime = SysCmd(acSysCmdRuntime)
    
Exit_IsRuntime:
    Exit Function

Err_IsRuntime:
    If (Err.Number = 5) Then
        IsRuntime = False
    Else
        MsgBox Err.Number & " - " & Err.Description
    End If
    Resume Exit_IsRuntime

End Function