Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

how to convert mdb file to exe

Oct 29, 2005 8:49PM PDT

Please help me how to convert an Access MDB file to EXE file, in order to run in a PC that dosn'd have a Microsoft ACCESS.

Discussion is locked

- Collapse -
Costly.
Oct 29, 2005 9:41PM PDT

Microsoft at one time had an Access developer's kit with a RUN TIME system for developers to compile and distribute an Access system. Its been years since I looked at it but it rang in at over 4,000 bucks.

Since then we moved to MySQL for the database engine (free, look on google.com) then Visual Basic for the frontend. If you code it right the enduser just hits return to install MySQL and MyODBC and your application.

The runtime cost for such an application is now zero and for us has been worth the time.

Cheers,

Bob

- Collapse -
Thank you very much Bob!!!
Oct 30, 2005 3:19PM PST

Thank you very much Bob!!! But can you pleas tell me how to do this and what (with programs or tools) I need for this. The cost is not so importent for me. I have so many jobs alrady done with MS ACCESS.

- Collapse -
Call mother.
Oct 30, 2005 8:31PM PST

The product was by Microsoft. It may or may not be available any more.

As to MySQL and client applications, the MySQL, MyODBC is easy to find and free to use from the web. Just google those names.

As to the client applications, if you've dabbled in VBA then move to VB or VB.NET and there are fine examples of using SQL from VB that make movement to a more stable system easy.

Cheers,

Bob

- Collapse -
Access runtime: $499
Oct 29, 2005 11:21PM PDT
- Collapse -
Runtime versus .EXE
Oct 29, 2005 11:30PM PDT

The runtime was an option for some, but failed us as we found that there are other requirements for the runtime to function.

For example, all the OS and system requirements for Office 2003 remain in full force even though you have just the runtime. There are also some features you can't use in the runtime that would work in the full version. Hopefully the author of the application didn't use those.

Our migration away from Access has been a boon to our bottomline plus we have stability that was only dreamed about back when we inherited the Access applications. We're not going back.

Bob