VBA versus VB EXE

[asafb]

Dear tek tips members:

I have an Access program I designed and I want to migrate it into its own self-made EXE file so that other users don't need Accessw.

What should I do?

What will happen to all the tables, queries, reports, etc.

 

[vbajock]

You can't use the Access objects as standalone components within a VB executable. You will have to rebuild them all from scratch. Have you looked at MDE's?

 

[Darrylles]

Hiya,

If you want to go to VB, then it means a total re-write. VBA and VB are 2 different entities, VB being a development tool in it's own right. VBA is an adaptation of VB allowing it to be used within other MS applications such as Access, Word, Excel etc.

If you want an executable of your MS Access application, then look at creating a .MDE from your Access application.
(This is an executable of your application).

I think the latter is what your after - look at the keyword: MDE in Access Help to point you in the right direction.

Come back with specifics if you have any.

Kind regards,

Darrylle





"Never argue with an idiot, he'll bring you down to his level - then beat you with experience." darrylles@totalise.co.uk

 

[wbwillson]

In addition to making your application an .MDE file (which compiles all of your VBA code so others can't view it), you can make an Access application that can be distributed to people without Access installed. You have to have the Developer edition of Microsoft Office which contains the Run-Time version of Access. This is a fairly high level approach and most likely an MDE would do fine but it will still require that the end users have access installed.

Bill