How to make and executable mdb file

[naveen prasad]

Dear all
Good day...
Kindly help me in this problem

I have prepared some reports , using queiries, forms, tables.

I have made 1 form as startup form.

now I require to make an executable file, which i want to put in different
pc's

when they click that file, they should be able to see only the startup form.
and other pages, like queires, tables, other forms.

waiting for your kindly help.

regards
naveen

 

[Douglas J. Steele]

It can't be done. There has never been the ability to convert an Access
application into an executable file in any version of Access (and I'm pretty
confident that there never will be, since having an executable which has to
constantly change itself would wreak havoc on any virus detection software!)

Assuming that you want to allow people who do not have Access installed to
use your application, you have 3 main options:

1) Rewrite your application in a language that can be compiled into an
executable such as VB or VC++ (note that your data will still have to be
kept in an external MDB file)

2) Rewrite your application as a web app

3) Get the Access Developer edition that's appropriate for whatever version
of Access you're using (see
http://www.granite.ab.ca/access/developereditionversions.htm for details of
what you need to look for) What this allows you to do is package your
application together with a royalty-free run-time version of Access. Users
who don't have Access installed will be able to install the run-time and use
your application. They will not be able to use the runtime to make design
changes to your application (nor to any other MDB)

 

[naveen prasad]

Noted dear
Thank you dear for your kind reply

I really dont know the use of this MDE file, there is an option in access to
make MDE file. kindly describe me what is the use of this MDE file.

secondly is there is any other option to hide my queiries , tables, forms in
the access file.

kindly give me reply.

regards

 

[Banana]

A MDE file basically strip out the VBA code and leave you with a file
with only compiled code. This means nobody can alter the forms or
reports or any code. Be aware this is a one-way operation so you will
need to hold on your original MDB file for further development and
re-distribution.

Note that MDE is distinct from runtime even though they can have same
effect (e.g. no design changes possible), the difference being that MDE
can't even be altered with a full version of Access installed while a
MDB file running on runtime can't be altered but can be by running a
full version of Access.

Furthermore, MDE does not protect the tables and queries. One still can
import/export and possibly alter those objects. If you want to protect
those, consider using User-level security to designate a different owner
and deny all permissions except to execute the object to the public.
That way, you don't have to get your users to join a custom .mdw nor do
you need to distribute .mdw. Just keep it to yourself and they only can
use what is allowed to the public role.

Alternatively, you may want to consider using a RDBMS backend to protect
the data. You still can link it to a MDE and not save the password so it
cannot be altered or controlled outside the intended usage.

HTH.

 

[naveen prasad]

Noted Dear,
Thanks alot for your kind information.

I will check your points to execute

thank you once again
regards