Selling runtime and want to make sure I've crossed all my T's

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am finishing up a database for a client who will be marketing it. She's
invested a large sum in the development and I want to make sure that I don't
miss anything. It's great tool and I hope it really sells well. I want to
make sure that someone can't steal it from her. I'm setting it up as a BE/FE
and am converting them to MDE's and then into runtime. I'm also copyrighting
the program for her. I'm concerned about the back end table design and that
someone could potentially view that. I was trying to avoid having to put in
security as I'm not sure how that would affect runtime. Any words or wisdom
on this issue and anything else I should make sure I do before she releases
it.

thanks so much.
 
Hi,
you can apply security to backend, in order to "hide" table structure - you
need to use queries with owner access permissions, and remove all
permissions from tables. but I am not sure that you really need this, not so
much valuable in table structure. I think making MDE will be enough
 
I made the front end into an mde to protect the code there. but the table
structure is visible from the back end. I know that access security can be
hacked so I was hoping for a more foolproof method. I also was trying to
avoid dealing with a whole mdw issue since i hadn't done that where it was
wrapped up in a runtime and I'm not sure how to change the short cut link in
runtime to accommodate it looking for a new mdw.

thanks
 
See Startup command-line options in access help:

/wrkgrp <workgroup information file>
Starts Access by using the specified workgroup information file. Applies to
Access databases only.
 
Alex said:
I made the front end into an mde to protect the code there. but the
table structure is visible from the back end. I know that access
security can be hacked so I was hoping for a more foolproof method.
I also was trying to avoid dealing with a whole mdw issue since i
hadn't done that where it was wrapped up in a runtime and I'm not
sure how to change the short cut link in runtime to accommodate it
looking for a new mdw.
Click to expand...

You think you've got a table structure that is so unique it is worth
stealing?

If you want to protect *data* from users then it should not be in an MDB
file. I can think of no reason to be worried about table design structures.
 
Back
Top