MS Access

jasmin10

I have a customer database which I have worked very hard on and want to prevent it from being copied.

i.e I tailor it to suit a customer, and I want to prevent them from giving/copying to other companiese but I want them to still be able to edit it etc.

I have looked at the security features but they are a bit confusing, can anyone help in laymans terms

superscaper

I'm not sure how easy it would be to physically stop them from copying it. If it was me I'd leave it and pursue them legally if they did pass it on. Just make it very clear that they are only allowed to have one copy and that you retain the copyright.

jasmin10

hello hello hello, we are going to have to stop meeting like this.

I didn't think it was an easy thing.

Something else though you may be able to help me with seeing as your the fountain of all knowledge.
I have a form in access, you know the one when in design view its background is a grey grid but views plain grey when in the proper form. I want to change the background to a picture that I have. I know how to change the colour but not to a wallpaper. Any ideas?

PierceUK

if you have created it in access you can make a .MDE file out of it. this protects all of your code (but not forms/tables)

try looking it up in the help provided.
I normally split my database first (so tables are in one file and everything else in the other)
and then create the MDE file. this just makes it easier to manage and a bit quicker over slow networks(all my access stuff is multi user fun.....)

PierceUK

P.S. Jasmin hijacking threads in frowned apon. but you could just add a unbound image and then "move to back" command on it.
Dont have access at home so dont know if there is an easier way of messing with the form options.

scottishlass

If you go to the help file -> adding a picture or object -> you should be able to click on the background option and it gives instructions which I usually find to be quite useful and since its been a while since I've done them - it probably explains it better than i could.

jasmin10

Figured it out thank you.

Hijacking threads???? what does that mean

jasmin10

Just found out what your on about.
So it's not allowed to create a thread about a particular then and than add in the same conversationa question about something else.

Get a life!, some folks on here are friendly and don't mind helping others out, including myself when I am able to.

PierceUK

Sorry Jasmin i didn't mean it to sound as harsh as it did.

superscaper

PierceUK,
I'd only consider it hijacking if it was someone else and not the OP. I don't think it's possible to hijack your OWN thread. I know some posters on here prefer that people introduce new threads for new problems but in this case it's a pretty closely related question and more of a "by the way" rather than a major one.

To be honest I didn't even know what you were going on about at first and who you were directing the statement at. Never heard of OP being accused of hijacking their own thread before.

jasmin10, hope suggestions made helped, I've not really had any need to use Access myself. Feel awful about putting across the impression I'm knowledgable and intelligent well I'm certainly not omniscient and my lack of access knowledge should demonstrate my fallibility

elite_2

Make sure they sign some kind of data useage agreement (I agree to only use this data for whatever purpose, however many of times..)

I then monitor their usage by inserting a contact that points to a address I have access to (make sure you tell them this in the fata useage agreement) - The name I change to reflect the company I'm giving it to.

e.g.

Supplying database to company 1 I would insert the following:

Mr A Jones
1 Station Road
Birmingham
B1 1AA

For company 2 I would insert:

Mr A Smith
1 Station Road
Birmingham
B1 1AA

(make sure you keep a record of which names you have given to which company...)

Hope this makes sence - might only be useful in mailing list senario

HTH

PS I assume you have all the data protection act stuff in place... (informed consent et al