Developers extension - stand alone ?

D

David Cleland

I am very pleased with my end application...... but I just checked the
folder within program files to find it puts a copy of the database in there-
what is to stop someone stealing your work from there ?

I thought the runtime was to protect the application ?

David
 
R

Rick Brandt

David Cleland said:
I am very pleased with my end application...... but I just checked the
folder within program files to find it puts a copy of the database in there-
what is to stop someone stealing your work from there ?

I thought the runtime was to protect the application ?

Nope. You can distribute an MDE instead of an MDB to protect your code.
You would have to implement User-Level security to protect anything else.
The former is completely effective while the latter can be hacked by the
determined.
 
D

David Cleland

Nope. You can distribute an MDE instead of an MDB to protect your code.


but an MDE requires access to be installed ? or can you run the extension
wizard on a mde ?

David
 
D

Douglas J. Steele

An MDE requires Access to be installed, but if you have Access Developer
Extensions (ADE), that's what it does: install a royalty-free run-time
version of Access for those who don't already have Access installed.
 
R

Rick Brandt

David Cleland said:
code.


but an MDE requires access to be installed ? or can you run the extension
wizard on a mde ?

Running either an MDB or an MDE requires Access to be installed. The
developer's tools simply allows you to include a crippled version that is
installed with your app. Your actual file is not altered in any way by the
developer's tools.
 
D

David Cleland

Running either an MDB or an MDE requires Access to be installed. The
developer's tools simply allows you to include a crippled version that is
installed with your app. Your actual file is not altered in any way by
the
developer's tools.
 
D

David Cleland

Running either an MDB or an MDE requires Access to be installed. The
developer's tools simply allows you to include a crippled version that is
installed with your app. Your actual file is not altered in any way by
the
developer's tools.

but if the person installs access they can then go to the folder and alter
the database - if it was an MBE in the folder that would stop it ?

David
 
A

Albert D. Kallal

but if the person installs access they can then go to the folder and alter
the database - if it was an MBE in the folder that would stop it ?

It would only stop them from modifying the forms, reports, code. It would
not stop them from modify the data.

As a general development practice, I sure you always distributed a mde to
your users. This good advice applies regardless of using the runtime.

And, as a general rule, it is assumed you are using a med when using the
runtime..but is not 100% a requirement.
 
D

David Cleland

And, as a general rule, it is assumed you are using a med when using the
runtime..but is not 100% a requirement.


So can I make an MDE then use the wizard to package the app up as I would an
MDB ?

Sorry what is a MED ?

David
 
D

Douglas J. Steele

David Cleland said:
So can I make an MDE then use the wizard to package the app up as I would an
MDB ?
Yes.

Sorry what is a MED ?

A typo for MDE?
 
A

Albert D. Kallal

So can I make an MDE then use the wizard to package the app up as I would
an MDB ?

Yes...as mentioned, it is generally assumed that by the time you get around
to using the runtime..you been using mde's. It is kind of a given assumption
since the runtime does not allow modifications of your applications..so you
might as well ensure that your application works as a mde. If you have some
code that modifies a form etc in desing mode, then it will not work as a
mde, and also will not work with the runtime. So, using a mde elimaontes
several possbilie issues and things you can do with a mdb, but not with a
mde. It just so happens that those same restrcitons appliy to the runtime.

Sorry what is a MED ?

Spell checker change that one!!...Typo......should have been mde...
 
Top