Deploy as ACCDE
I have an accdb database. I want to deploy it as an executable that will run without any installtion of MS Access on the client's PCs. Each time I run the Make ACCDE wiz I get MS Access was unable to create the accde... The help says it can create a mazimum of 2048 TableIDs. My database is small with 9 tables, 27 queries, 9 forms, no modules but underlying modules for all forms.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What version of Access are you running?
Note that you cannot create an accde file from an access 2003 format DB.
In other words, if you want to create an accde file, the database must be in the Access 2007 format
It may also be that you had a lot of tables over the life of the DB.
Have you run the Compact /repair utility lately?
Also try creating a new db and importing all the objects.
Note that you cannot create an accde file from an access 2003 format DB.
In other words, if you want to create an accde file, the database must be in the Access 2007 format
It may also be that you had a lot of tables over the life of the DB.
Have you run the Compact /repair utility lately?
Also try creating a new db and importing all the objects.
ASKER
I am using MS Access 2010 and want a deployable solution that will not need an installation of MS Access to run.
For sure you will need this:
A2010 Runtime - Free
http://www.microsoft.com/downloads/details.aspx?familyid=57A350CD-5250-4DF6-BFD1-6CED700A6715&displaylang=en
mx
A2010 Runtime - Free
http://www.microsoft.com/downloads/details.aspx?familyid=57A350CD-5250-4DF6-BFD1-6CED700A6715&displaylang=en
mx
ASKER
I have the runtime version. What I do not have is the knowledge on what to do to create an application that will take the runtime version and my database and deploy this as an executable program.
There is no such thing as a Executable Access program per se. You will need an installation program that, among other things ... installs the Runtime module and your related db files, etc.
Take a look at these:
Free Installers:
http://www.thefreecountry.com/programming/setup.shtml
mx
Take a look at these:
Free Installers:
http://www.thefreecountry.com/programming/setup.shtml
mx
To summarize the posting above, in order to deploy your database to end users who do not have Access, you must do these things:
1) Compile the database to the ACCDE format. MX has given you the steps necessary to do that successfully
2) Obtain the Access 2010 Runtime
3) Use an installer of some sort to deploy both the 2010 Runtime and your compiled .accde file.
In a nutshell, those are the steps needed to deploy your database to another machine that does not have Access installed.
However, understand that if that machine DOES have Access installed (any other version), then deploying your db with the Runtime can wreak havoc on the machine. Many who must deploy in this environment use Sagekey to build their deployments (www.sagekey.com). It's pricey, but it also insures that you don't muck up the end user machine.
There are also several differences when dealing with a Runtime version of Access vs a Retail version:
http://msdn.microsoft.com/en-us/library/cc136539(v=office.12).aspx
The article is for 2007 but everything still applies to 2010.
1) Compile the database to the ACCDE format. MX has given you the steps necessary to do that successfully
2) Obtain the Access 2010 Runtime
3) Use an installer of some sort to deploy both the 2010 Runtime and your compiled .accde file.
In a nutshell, those are the steps needed to deploy your database to another machine that does not have Access installed.
However, understand that if that machine DOES have Access installed (any other version), then deploying your db with the Runtime can wreak havoc on the machine. Many who must deploy in this environment use Sagekey to build their deployments (www.sagekey.com). It's pricey, but it also insures that you don't muck up the end user machine.
There are also several differences when dealing with a Runtime version of Access vs a Retail version:
http://msdn.microsoft.com/en-us/library/cc136539(v=office.12).aspx
The article is for 2007 but everything still applies to 2010.
MX mentions this as Point #6B of his first post, but it is buried in there, so I thought I would reiterate.
If your system will not create the mde for you, then you likely have compile errors.
Open the VBA window, then select the Debug -> Compile option from the menu.
Once you have fixed all of the compile errors, you should be able to create the accde file, but I would follow MX's instructions to the letter!
If your system will not create the mde for you, then you likely have compile errors.
Open the VBA window, then select the Debug -> Compile option from the menu.
Once you have fixed all of the compile errors, you should be able to create the accde file, but I would follow MX's instructions to the letter!
Seems like MX mention pretty much everything ... a whole bunch of stuff, including steps 1,2 3 mentioned by LSM. Wow!
Glad I could be so darn helpful !
mx
Glad I could be so darn helpful !
mx
Meanwhile ... Just to be *sure* your ACCDB is 'clean' before creating the MDE, run this procedure ... we may get lucky:
Open the VBA Editor and from the menu ...Tools>>References ....
If you see any listed as **Missing: <reference name>, including the asterisks and the word Missing, the
you need to fix that first.
Then, follow this procedure:
****
0) **Backup your MDB BEFORE running this procedure**
****
1) Compact and Repair the MDB, as follows:
Hold down the Shift key and open the MDB, then from the menu >>Tools>>Database Utilities>>Compact and Repair ...
Close the mdb after the Compact & Repair.
2) Execute the Decompile (See example syntax below) >> after which, your database will reopen.
3) Close the mdb
4) Open the mdb and do a Compact and Repair (#1 above).
5) Close the mdb.
6) Open the mdb:
a) Right click over a 'blank' area of the database window (container) and select Visual Basic Editor. A new window will open with the title 'Microsoft Visual Basic' ... followed by then name of your MDB.
b) From the VBA Editor Menu at the top of the window:
>>Debug>>Compile
Note ... after the word Compile ...you will see the name of your 'Project' - just an fyi.
7) Close the mdb
8) Compact and Repair one more time.
*** Executing the DeCompile **EXAMPLE**:
Here is an **example** of the command line syntax (be SURE to adjust your path and file name accordingly) before executing the decompile:
Run this from Start>>Run, enter the following command line - **all on one line** - it may appear like two lines here in the post:
Also, the double quotes are required.
"C:\Program Files\Microsoft Office\Office\Msaccess.exe
For more detail on the Decompile subject ... visit the Master on the subject (and other great stuff) Michael Kaplan:
http://www.trigeminal.com/usenet/usenet004.asp?1033
AND ...
Once you get familiar with the Decompile idea (and ALWAYS make a BACKUP first!) ... you can add both Decompile and Compact/Repair to the Right Click menus in Windows Explorer, which I use multiple times daily:
Getting the Decompile and Compact context menu options
http://access.mvps.org/access/modules/mdl0039.htm
mx