Hosting DB on a network server

[lilFlip]

Hello,

I have a database that will be installed on a network server and then accessed by the client workstations. I want to be able to lock down the db to that particular machine, so that the client cannot port/copy the db to any other machine and then run it from there. Is this possible to do? Has anyone attempted anything like this before, and if so how did you accomplish such a task?

The reasoning behind doing this is to prevent the client or employee from taking the db and going to another company and implementing it for free.

Thanks in advance.

 

[Phonik]

That really depends on what type of network you are using and what software is running the network. Novell networks allow access rights to files but you would need to allow full access in order for users to be able to use the database. You could look into this a little bit more though.
You could also try making an mde file of your database so that even if somone does copy your database, they will not be able to edit/customise it as the design features are removed.

Gaz

 

[lilFlip]

Gaz,

Thanks for the reply. I'm not too worried about them modifying the contents of the db other than through the established forms. I have implemented the Security outlined through another thread on this forum provided by Mr. Len Boorman (I must say that it was quite easy to do with his instructions).

This security implementation provides me with the ability to keep them out of the design of the tables/forms/reports/etc and the data from the tables as well.

The issue I am trying to prevent now is the copying of the db to another computer at a different location and using there for free. I want to be able to charge for each instance of the application that is being used in a production environment. I know that with an Installshield, I could probably post something into the Registry on the server that is hosting the application but I'm not sure if there is a way that when a client workstation logs into, to check to see if the Server registry contains the key. Does this make sense?

 

[The_Doc_Man]

You cannot prevent copying a usable DB because to use it at least requires READ access.

What you COULD do is find some information about the drive hosting the database and then refuse to run if not in the right place. You would need to implement the DB as an MDE to make this a harder nut to crack.

 

[lilFlip]

Doc Man...

Thanks for the information.