By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,222 Members | 1,129 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,222 IT Pros & Developers. It's quick & easy.

Access Database to Executable File

P: n/a
Is there a way to convert an entire access database file (*.mdb) to an
executable file (*.exe)? This database will be on alot of computers,
and I really do not want to put Microsoft Access on each computer, due
to Microsoft licensing and everything.

Signed,
Charles Robinson III
ro******@saiyanprincefox.cjb.net
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On Thu, 23 Oct 2003 18:41:34 GMT, Charles Robinson III wrote:
Is there a way to convert an entire access database file (*.mdb) to an
executable file (*.exe)?
No.
This database will be on alot of computers,
and I really do not want to put Microsoft Access on each computer, ...
You don't have to. What you need is the developer edition for your office
version:

A97: Office Developer's Edition.
A2k: Microsoft Office Developer.
AXP: Office XP Developer.
... due to Microsoft licensing and everything.


Check the licence agreement for "runtime version".

Peter

--
No mails please.
Nov 12 '05 #2

P: n/a
TC

"Charles Robinson III" <ro******@saiyanprincefox.cjb.net> wrote in message
news:qt********************************@4ax.com...
Is there a way to convert an entire access database file (*.mdb) to an
executable file (*.exe)?
As the other respondent said: No.

This database will be on alot of computers,
and I really do not want to put Microsoft Access on each computer, due
to Microsoft licensing and everything.


If you know for certain, that the other PCs *will not* already have Access
installed, then maybe the developer (runtime) version will do the trick for
you. But if they *might* already have Access installed, then, installing the
runtime version could clobber their other Access programs! They probably
will not thank you for that. A whole industry has grown up around 3rd party
scripts to control the runtime installation process, to avoid such problems.
So in that scenario, you would be better (IMO) to change you mind, &
*require* them to have a copy of Access already installed on their PCs.

HTH,
TC
Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.