Conversion of an MS Access application

[Oldie]

I have built an MS Access Application under MS Office XP (but I also
own MS Office 2000). I have split the application in the pure database
tables and all the queries, forms, reports and macro's.

Now i want to use this application for different foundations in the
Netherlands but I want to secure my application so no one can change
it, copy it or steal it from me. I always thought there was a kind of
conversion tool that would translate the whole application into an EXE
program. But I understood from the different discussions that I have to
translate my MDB's to MDE's and add an Access run program to it. In
this case I can in no way prevent people from stealing my database
concept with all the tables and relations neither can I prevent them to
copy things. Is there a better solution available somewhere and what
does it cost?

I am a very experienced computer user (since 1958) and PC user and
consider myself as a database expert!

Eagerly looking forward to any solutions

[Tom van Stiphout]

On 25 Feb 2006 12:09:11 -0800, "Oldie" <ke*@hiquad.dem on.nl> wrote:

Then you should know there is no such thing as perfect security.

MDE protects against stealing your code: only the compiled version is
there, and your app is probably not THAT important that someone would
bother decompiling it.

One option is to use Access security. Download, study, and fully
understand the Access Security FAQ from microsoft.com before
proceeding. Again as an expert you already know all of this, plus you
know that this security can be broken by any number of password
crackers available on the Internet.

Another option is to protect your app with a dongle: a hardware key
that goes in the serial, parallel or USB port, and if not found by
your code, your app won't run. I've used products from aladdin.com and
they were straightforward to work with.

The database design cannot be protected given what I said about Access
security. Consider it your gift to the world :-) or consider another
database platform with higher levels of security available, such as
SQL Server 2005 Express Edition.

-Tom.

I have built an MS Access Application under MS Office XP (but I also
own MS Office 2000). I have split the application in the pure database
tables and all the queries, forms, reports and macro's.

Now i want to use this application for different foundations in the
Netherlands but I want to secure my application so no one can change
it, copy it or steal it from me. I always thought there was a kind of
conversion tool that would translate the whole application into an EXE
program. But I understood from the different discussions that I have to
translate my MDB's to MDE's and add an Access run program to it. In
this case I can in no way prevent people from stealing my database
concept with all the tables and relations neither can I prevent them to
copy things. Is there a better solution available somewhere and what
does it cost?

I am a very experienced computer user (since 1958) and PC user and
consider myself as a database expert!

Eagerly looking forward to any solutions

[Albert D. Kallal]

You most certainly can, and should hide all of the ms-access interface. The
options to complete hide and keep people out of the ms-access interface can
easily be done using the tools->start-up options. Using those options allows
you to complete hide the ms-access interface (tool bars, database window
etc). Also, using these options means you
do not have to bother setting up security.

Try downloading and running the 3rd example at my following web site that
shows a hidden ms-access interface, and NO CODE is required to do
this....but just some settings in the start-up.

Check out:

http://www.members.shaw.ca/AlbertKal...s/DownLoad.htm

After you try the application, you can exit, and then re-load the
application, but hold down the shift key to by-pass the start-up options. If
want, you can even disable the shift key by pass. I have a sample mdb file
that will let you "set" the shift key bypass on any application you want.
You can get this at:
http://www.members.shaw.ca/AlbertKal.../msaccess.html

The only additional things you really need to do to the above sample would
be to convert it to a mde...

I also have some screen shots..and some ideas as to how I use custom menu
bars in ms-access here:

http://www.members.shaw.ca/AlbertKal...erFriendly.htm
Also, I might as well give some ideas as to how one develops once you setup
the startup options...

Of course, during development, you will hold down the shift key so your
startup settings don't run. You then develop for awhile, and then to test in
"user" mode, you exit..and then re-enter the application without the shift
key bypassed. You will likely do this dance all day long as you run/test as
user mode, and then flip back in to developer mode (shift key used..so you
don't get the main custom menu). So, you can't develop, or really modify
things when you run your application with the startup settings...so you must
shift-by-pass them when you want to work.

And, in fact, I use alt-f4 to exit the application...t he mdb file should
still be highlighted in the windows explore..so, then you hit enter key
(and, hold down shift key if you need be). This key stroke sequence and
exiting and re-entering the application will occur CONSTANTLY all day long
when you are developing.

When you finally have things just right...you create the mde
you plan to distribute...

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl************* ****@msn.com
http://www.members.shaw.ca/AlbertKallal

[Albert D. Kallal]

>I always thought there was a kind of

conversion tool that would translate the whole application into an EXE
program.

no, you do have a essentially the same concept here, as a mde is your
executable. You can purchase a developers edition of ms-access, and thus
deploy your mde file to machines that don't have ms-access installed. Be
aware, that this runtime system is in effect a full ms-access install, but
with just the design abilities removed (so, this is a large install). I
can't really think of any software that works with a database that is a
simple .exe file these days anyway (That kind of went out with the slide
rule....).

The ms-access runtime for a2000 was a 150 megs in size (not the best for
downloading over the web for example). However, the a2003 runtime is a more
manageable 33 megs in size.
http://support.microsoft.com/default...b;en-us;842004

http://msdn.microsoft.com/library/de...sofruntime.asp
http://support.microsoft.com/default...b;en-us;842004
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl************* ****@msn.com
http://www.members.shaw.ca/AlbertKallal

[Lyle Fairfield]

Albert D. Kallal wrote:

You most certainly can, and should hide all of the ms-access interface. The
options to complete hide and keep people out of the ms-access interface can
easily be done using the tools->start-up options. Using those options allows
you to complete hide the ms-access interface (tool bars, database window
etc). Also, using these options means you do not have to bother setting up security.

I would very much like to hear the opinions of those who are more
familiar with Access Security than I about this statement, "using these
options means you do not have to bother setting up security".

[Larry Linson]

"Lyle Fairfield" <ly***********@ aim.com> wrote

I would very much like to hear the opinions of
those who are more familiar with Access Security
than I about this statement, "using these options
means you do not have to bother setting up security".

I view the Startup Options as being more for keeping casual users from
stumbling over their own keystrokes and inadvertently causing problems. They
certainly won't keep a serious, experienced Access hacker from stealing your
objects or code or the user's data.

On the other hand, neither will Access security prevent someone to whom your
data or application is worth approximately US$150. That's a price for which
they can buy one of several "password recovery software" packages.

Because of this, I don't worry much about the security of the application
and code (I don't create database applications for "general distribution",
except examples that I purposely leave "open"), and typically rely on the
security of the server DB back end to secure the data. Fortunately, most of
my clients have had an honest workforce whom they trusted and no one else
had access to the DBs.

Larry Linson
Microsoft Access MVP

[(PeteCresswell)]

Per Albert D. Kallal:

that this runtime system is in effect a full ms-access install, but
with just the design abilities removed (so, this is a large install)

When running under a .MDE, can the user change page setup specs on reports?
If so, do the specs persist?
--
PeteCresswell

[Oldie]

As one Dutchman to an other: thanks very much! Yes I know all these
things, but I am quite sure that there has been (in the days of Access
2 or 5) a real compiler!
I wondered if MS has given this up or if there are new tools under
Visual Studio that I don't know.I have no knowledge at all of Visual
Studio.

[Oldie]

Thanks very much for your good support! I have immediately addopted
your Shift Enable/Disable key utility.
The problem is that i have the database on my own network but I am not
working anymore (being nearly 68). There are at least 4 or 5 companies
(foundations) that want to use my database program for their end-users
on private isolated PC's at home. There is not much I can do to make
them memeber and things like that. It will be to complicated to
distribute it this way.. But disabling the shift key and hiding the
Access toolbars is at least a good start.
Thanks very much for your ideas.
But I am sure there was a compiler in the days of Access 2 or 5. Maybe
it is in Visual Studio (I don't know this package).
I just want to help these foundations with just spending my time and
not my money!

[Oldie]

Thanks for your answer. I am from the time of the slide ruler and
studied math. But I am sure this tool was still there in Access 2
and/or 5.
My "clients" are volunteers helping f.i. heart and kidney foundations
to raise money. They work on their private PC's at home and in most
cases they don't have Access installed on their machines.