mdb 2 exe

[mike via AccessMonster.com]

Hi,

does anyone know if it is possible to convert an access database (.mdb) to a
stand alone (.exe) format. Or if someone has designed any software to do this
and maintain all the access functions?

also; on a similar note; how do you create an install screen for a file, that
will install the file and place an icon on the desktop and in the start menu?

thanks everyone;

 

[Douglas J. Steele]

There's no way to turn a DB into an executable. 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 make design changes to your
application (nor to any other MDB)

The Developer edition comes with an installer, but many people are
dissatisfied with its capabilities and go with 3rd party solutions. SageKey,
at http://www.sagekey.com/ , is one that a lot of people recommend.

 

[TC]

Further to Douglas's options:

4) Require (as a condition of using your software) that the user has a
working copy of Access already installed on their PC.

Believe me, that is a lot simpler than trying to deploy the runtime
version.

HTH,
TC

 

[Douglas J. Steele]

Yeah. Good point.

 

[Bruno Frisque]

Yes, this is very very true .
(Access Runtime is wonderfull, if app was designed for, but a "Nightmare" if
installation problems ..)

 

[Chris Mills]

Hi Bruno,

Regarding that issue (I assume MS Dublin is asleep still!), is there any
chance you can get that PC to install full Access?

If it is caused by Access Runtime vs Full Access, as against some other issue,
here's a chance to prove it!

I'm not convinced that there's a problem with Access Runtime as such (it's the
same program!), and there seem not many reports knocking Runtime. I cannot say
the same for ancilliary issues (PDW, references, versions, etc), but a lot of
that would be common issues anyway.

Chris

 

[TC]

I made the decision long ago, never to use it. That's not because I
had any personal experience with it! It was all because of third-party
products like Sage.

If a technology (such as the Access runtime) needs third-party products
before you can use it safely in the "real world", that's a good reason
to stay away from that technology, IMHO!

Cheers,
TC

 

[Bruno Frisque]

Hi Bruno,

Regarding that issue (I assume MS Dublin is asleep still!), is there any
chance you can get that PC to install full Access?

YES Dublin is not yet reacting !!! but reminder sent by MS France today ..
(must be too busy ??)
Installing a full A2K at customer site was refused by the customer. Risk to
jeopardise their vendors apps relying on Off 97 !
Wait and see .....

 

[TC]

If you start A2K and then close it, all subsequent opens of any MDB
file (by double-clicking it) will try to open it with A2K. Similarly,
if you start A97 and then close it, all subsequent opens of any MDB
file (by double-clicking it) will try to open it with A97. So, there
definitely can be problems in a mixed environment when you open
database files by double-clicking them. For example, if you ran A97,
then double-clicked an A2K MDB file, it would try to open the A2K file
with A97, which will fail with an error.

One solution is to ensure that all databases are started via a shortcut
which selects the proper version of Access.

HTH,
TC