Avoiding unauthorised copying of MS Access db to another Machine

[Demerit]

I was kind of wondering whether there is a means to secure an access db such that it can be installed in a machine like other programs. Then prevent it such that when someone copies the files in "program files" to another machine without authorisation, it should not work.

I will be glad to get your suggestions.

[June7]

Research publishing database as an executable and licensing.

Here is one http://social.msdn.microsoft.com/For...orum=accessdev

[ItsMe]

If your DB uses code to hide objects like tables, etc. You could store information about the machine in a table. Code during startup could compare the information in the table with the current machine.

[Demerit]

Hello ItsMe, How and what code can i use?

any samples, I will be gratefull having it.

[Xipooo]

You can also check the name of the computer by using Environ$("Computername").

[ItsMe]

       
        Dim objShell As Shell
        Dim strComponent As String
        Dim strAnswer As String
        Set objShell = CreateObject("shell.application")
        
        strComponent = ""
        strAnswer = ""
        
        strComponent = "ProcessorSpeed"
        strAnswer = objShell.GetSystemInformation(strComponent)
        Debug.Print "ProcessorSpeed = " & strAnswer & vbCrLf
        
        strComponent = ""
        strAnswer = ""
        
        strComponent = "ProcessorArchitecture"
        strAnswer = objShell.GetSystemInformation(strComponent)
        Debug.Print "ProcessorArchitecture = " & strAnswer & vbCrLf
   
        strComponent = ""
        strAnswer = ""
        
        strComponent = "PhysicalMemoryInstalled"
        strAnswer = objShell.GetSystemInformation(strComponent)
        Debug.Print "PhysicalMemoryInstalled = " & strAnswer & vbCrLf
   
        strComponent = ""
        strAnswer = ""
        
        strComponent = "IsOS_DomainMember"
        strAnswer = objShell.GetSystemInformation(strComponent)
        Debug.Print "IsOS_DomainMember = " & strAnswer & vbCrLf

        Set objShell = Nothing

[Demerit]

From the code above, what can i use as the table fields and data type? Can I put the code on the UnLoad Event of my first form when the db is opened? In the code above I have not seen a reference to a recordset as well. and what will be the condition if those things do not match what is on the table?

[ItsMe]

From the code above, what can i use as the table fields and data type?

The code above works independent from queries and tables. If you place it behind a form, maybe in a click event, you can pull system information and have it print in the immediate window. You will need to come up with a plan to compare system information, retrieved from code, to a table that stores previously retrieved data. So, the first time the app runs it will pull data from the machine and store it in a table. Also, it would change a condition, like a Boolean, to indicate that the table is populated and said information is the benchmark for subsequent application startups.

Can I put the code on the UnLoad Event of my first form when the db is opened?

I suppose you could. I would probably have it run first thing during startup. Code would determine if this is the first time the app is being run by looking for data in the previously mentioned table or a status Yes/No field. Code would then decide whether or not to pull system info and compare (depending on the status). The result of the initial code would then determine if the app goes forward with startup or halts and gives the user a message by opening an alternate form.

In the code above I have not seen a reference to a recordset as well. and what will be the condition if those things do not match what is on the table?

As I mentioned. There is no recordset or query involved in the code provided. The code just looks at the system info and prints it to the immediate window. You can view the Immediate window in the VBA editor. The keyboard shortcut is Ctrl+G. What you do with the information still needs to be determined when you create a table and, as you mentioned, a recordset to interact with the table. You need to take a look at what the code provides and determine if it will suffice.

Unfortunately, I could not find VBA to pull the serial number from the CPU. The only examples I could find were in C++ and C#. I found a hint of some success using VB6 and the DLL that C++ depends on but did not get too adventurous to see if I could get it to work in VBA. Right now, I do not even remember the reference that C++ uses. I probably should have made a note of it.

When I originally posted, I thought I saw some examples of VBA getting real, substantial, system info. Now I can not seem to find any. The info that the code I posted here is stuff that could be easily changed and or replicated from one machine to another. It may or may not be adequate for your needs.