Legal use of .mdb files in a commercially distributed program

[Guest]

I've written an access database (.mdb) and a program in C# that uses the data
in this database, but only in read mode. No changes are made to the .mdb by
the program.

1) If I distribute this program commercially are there any legal
implications I need to consider? I have a legal version of Office 2003. I
don't expect the users to have MS access.

2) If I password protect the database, how safe would this database be from
piracy

3) Is there a safer and more cost effective solution that you would suggest?
Thanks,
Tim.

 

[Douglas J. Steele]

1) No implications that I'm aware of (but then, I'm not a lawyer...). It's
no different than distributing a .DOC or .XLS file.

2) Not particularly. There are lots of password crackers available.
Realistically, if they can get to the physical file, they'll likely be able
to get at the data.

3) SQL Server Express (or whatever it's called these days) is another
alternative. Don't know whether it's any more secure.

 

[Guest]

Thanks Doug. That was quick

It's good to know that I can probably use access without any implications.
I'll have to think on it though. I'd like to use access as it'll save a lot
of time, but I'm also keen to protect my data as that's the most labour
intensive part of this project.

Do you know if there are utilities that can encrypt the data in a .mdb file,
so that if they crackers do manage to access the data, then they'd also have
to decrpt it?

I'm guessing the best I can do is make it difficult rather than impossible,
as we're just a very small outfit doing this in our spare time. We have to
way the benefits and costs carefully.

Thanks again.

 

[Douglas J. Steele]

Access has the ability to encrypt itself, but again, if they have access to
the physical file, it's virtually impossible to prevent a determined
individual from getting to its contents.

There may well be other encryption products out there: I haven't looked for
them.

 

[David Cox]

Have you considered encrypting some of the data (e.g name address, chemical
ingredients, recipes) in C#, where you can make it as secure as you like?

 

[Jamie Collins]

Thanks Doug. That was quick

It's good to know that I can probably use access without any implications.

I think Doug was saying you can use (and distribute) the mdb *file*
without implications.

You are presumably accessing the mdb file using Jet via the MS OLE DB
provider, both of which are available as a free MS download (including
a redistributable versions), so no problems there either. However,
AFAIK the Access application (including run time version) requires a
licence to be distributed and/or installed.

Jamie.

--

 

[Douglas J. Steele]

I think Doug was saying you can use (and distribute) the mdb *file*
without implications.

You are presumably accessing the mdb file using Jet via the MS OLE DB
provider, both of which are available as a free MS download (including
a redistributable versions), so no problems there either. However,
AFAIK the Access application (including run time version) requires a
licence to be distributed and/or installed.

Exactly. Of course, since Timski said "I've written an access database
(.mdb) and a program in C# that uses the data
in this database, but only in read mode.", I didn't think it was necessary
to include that caveat.