How to make file executable

[mopat]

Hey guys,

Does anyone know how to make a file executable without opening access so that it would just be an icon that sits on the desktop?

Thanks!

 

[ghudson]

you cannot convert an Access database file into an executable .exe file

 

[boblarson]

Hey guys,

Does anyone know how to make a file executable without opening access so that it would just be an icon that sits on the desktop?

Thanks!

That question has been asked so many times on this forum it would make your head spin. It would be good if you tried using the search facility first.

 

[missinglinq]

So that's what your avatar represents, Bob!

 

[boblarson]

So that's what your avatar represents, Bob!

Yep, the spinning head.

 

[mopat]

Hey guys,

Before anything, Im fairly new to access so I apologize in advance if I dont understand something but,I tried doing some research on google and on this forum to make an access file executable. there are a couple things Im confused about

As of now, I have a file that has a form and subform linked to a query.

My goal is for users to open the file as a runtime so they could do simple searches.

The first thing I did was downloaded the Access Runtime extension and also the developer extension. I read somewhere I had to save the file as an .MDE file in order to protect that data. But then I read I had to save it as an ACCDE file.


Im really not sure what im doing here, feel like im going in circles trying to figure out the right steps. It would be greatly appreciated if someone can help me out with the proper steps.

Thanks!

 

[boblarson]

An ACCDE file is the format that is created when you compile an ACCDB file (2007/2010 format). If you have an MDB file, compiling that will create an MDE file. They are essentially the same thing (ACCDE/MDE) as they are compiled versions of their respective full open database format. Compiling will lock down design changes to macros, modules, forms, and reports.

The runtime can use both ACCDB/ACCDE or MDB/MDE files. You do NOT have to compile them to use them with the runtime. However, if you do not then you will have to provide "bullet proof" error handling as runtime errors will cause your program to crash if you use an uncompiled version.

Hope that helps.

 

[mopat]

Thanks Bob, Im a lot less confused about the different formats and which would be acceptable for a executable file.

The thing is im still stuck on making it into an executable file. Is it possible I can get a step by step list of how to go about this? I would be very grateful.

thanks,

 

[boblarson]

Again - you do NOT turn it into an executable file. You give the user the mde/accde etc file and have them install the runtime. The runtime is basically Access but without the ability to make design changes.

The packaging wizard in the developers extensions makes it so you can create an installation routine that will install the runtime and place the database file and any supporting files you include on the machine.

But if you are just working with people at work then you can just install the runtime on their machines and place the frontend on their machine.

But again - there is no "creating an executable" when it comes to Access.

 

[mopat]

Oh ok I understand. So what I really am trying to accomplish is creating a "frontend" for users to have access to.

If i did create a front end, would user still have to open access than the file or can it be opened through an icon on the desktop

 

[DCrake]

Can you clarify that the end user does (not) have Access installed on their machine in the first instance. This makes a big difference.

 

[mopat]

The user would have access installed.

 

[DCrake]

Then you do not need to worry about creating an executable file (even though you can't). Simply deploy a MDE or ACCDE file to the end user. As long as you retain the uncompiled version for development purposes then you should be alright.

 

[mopat]

Im sorry because Im fairly new im not sure how to deploy a MDE or ACCDE file to the end user.

Will it be accessible through an icon without showing Access 2007 running?

 

[boblarson]

Im sorry because Im fairly new im not sure how to deploy a MDE or ACCDE file to the end user.

Depending on how many users you have you can

1. Email it to them.

2. give them a batch file which would copy it from a network location.

3. Go around to each computer and copy it for them to their desktop.

For updates, check into an auto updater (like my free frontend auto update enabling tool available here or Tony Toews' free auto updater)

Will it be accessible through an icon without showing Access 2007 running?

No, Access will be shown. Even if you use the runtime the Access window will be shown. There are some coding things you can do to make it NOT show but trust me - it isn't worth the hassle. I went there once; ONCE and never returned.

 

[mopat]

Great info thanks!

So what steps would have to be taken?

Create a frontend for users
Email it to them or store it on a shared network?

 

[boblarson]

Great info thanks!

So what steps would have to be taken?

Create a frontend for users
Email it to them or store it on a shared network?

This is the method I use:

1. Have split the database into the frontend/backend with tables only in the backend.

2. The frontend is now a master copy. I keep that somewhere on the network where I can work on it.

3. I make a copy of the frontend and if I have 5-10 users I will just go around to their computer and copy it from the network to a location on their desktop.

4. If I have more than that I will create a batch file which will copy it to their machine and then email it out.

 

[ChipperT]

By the way, if you use the Access Developers Extension to package your application, you can specify a custom icon that will appear on the user's desktop on in their start menu. They simply click on that icon and start the application. If you have hidden nav panes, etc it can appear to the user as just another program on their desktop or start menu.

 

[mopat]

Hey bob,

I tried to split the databases but for some reason when i did they dont seem to actually work. I used the method within this link for Access 2007

http://support.microsoft.com/kb/304932

when trying to complete searches within the forms on the front end or back end they dont work. is it suppose to be like that?

Chipper,

If i use the access developer extension package would I still have to split the forms? Or would I just be able to run the search without having access visually running on the screen.

 

[boblarson]

when trying to complete searches within the forms on the front end or back end they dont work. is it suppose to be like that?

There should not be any forms in the back end - ONLY TABLES go in the backend.
Apparently you didn't do exactly as the article said.

To boil it down to this easy method:

1. Take your unsplit database and make a copy of it.

2. In the copy go in and delete everything but the tables.

3. In the first one go in and delete the tables.

4. Go to EXTERNAL Tab and do an IMPORT but LINKING the tables instead of importing. You select the one with just the tables to link to.

5. There, you have a split database and you ONLY use the Frontend, the backend is just where the data is stored.