Topics Search

Unable To Create An Accde File

Unable To Create An Accde File
Views: 8
I have a db that I am attempting to create an accde file of. it has a FE/BE and I compiled the DB and that's fine. For some reason, I am getting an error:

Microsoft Office Access was unable to create the .accde, .mde, or .ade file message.

When I click on show help it explains

This error is usually associated with compiling a large database into an MDE file. Because of the method used to compile the database, a considerable number of TableID references arecreated for each table. The Access database engine can only create a maximum of 2048 open TableIDs at one time. Exporting a database as an MDE potentially can exceed this limit if thedatabase has a large number of objects (table, macro, form, report, etc)...
Sponsored Links:

More topics

 

Unable to make ACCDE

Preview
how i prepare ACCDE file, when i click that button it will give some error msg. like "Microsoft office access was Unable to create the .accde, .mde, or .ade file".

Can anybody help me to resolved this issue..
I am using Access 2007.
file type .accdb
 

dont create accde file

Preview
I try to create accde file in access 2007 but he give me this msg " microsoft office was unable to create .accde,.mde or .ade file
 

Unable to make ACCDE

Preview
When I click that button it will give some error msg. like "Microsoft office access was Unable to create the .accde, .mde, or .ade file".

I am using Access 2007.
file type .accdb
 

ACCDE Recisions

Preview
With my db completed I created an ACCDE file, I then realised I needed to change something so I went back to the original file, but this would not reflect in the ACCDE file obviously, so I create a new ACCDE file. The problem is that I then have to tell it again which is the startup page, to remove the nav bar, to minimize the ribbon, to point to the icon etc. etc.

I may do another 50 revisions this month, isn't there a way of updating the accde file back to the original whenever I make a change?
 

How to make 32-bit ACCDE from 64-bit Access 2010

Preview
Is there a way to compile a 32-bit ACCDE file from an Access 2010-64 ACCDB file? I have a client who has both 32 & 64 bit systems and I have an automated way to create a 64-bit ACCDE but a 64-bit ACCDE will not run on their 32-bit systems.

So I need to add code (if possible) to create a 32-bit ACCDE from a 64-bit system.

Here is the code that creates the 64-bit ACCDE:

Set AccessApplication = New Access.Application
With AccessApplication
.AutomationSecurity = 1 'MsoAutomationSecurityLow
.UserControl = True
.SysCmd 603, sourcedb, targetdb 'this makes the ACCDE file
.Quit
End With

Is there a way to change this code to create a 32-bit ACCDE as well as the 64-bit one?
 

Accdb makes accde without VBA

Preview
After working on the accdb, complied it and created the accde. Now unable to use the accde. None of the buttons on the main menu worked. When we got here, we created a new accde using the same accdb. The newly created accde also does not work. It is as if all the code is gone. However the accdb is working great.

I checked the trust. I compiled, compacted and repaired.

Any other ideas on what happened and how to fix?
 

Disable the F4 key in ACCDE

Preview
I've created a database and I distribute the front end using the ACCDE format. One of the forms I have is set to open Read Only and I have disabled editing, deleting, etc., in the property sheet.

However, when I create the ACCDE I hit a problem. On opening the ACCDE file, I click the button to open the form and all works well. However, I can press F4 and it shows the Property Sheet where I can change values to allow editing.

Is there any way to disable the property sheet in the ACCDE file
 

Needing more info about using Access runtime vs. ACCDE

Preview
I'm trying to understand Access Runtime, as compared to an ACCDE file.

1) If I use Runtime, does it eliminate the need to hide the navigation pane, menus and ribbons?
2) Does it create an executable file that can be used on any computer, regardless of whether Access is installed or not?
3) Does Runtime need to be previously installed on the Users' computers?
4) Is a Runtime file a smaller footprint than an ACCDE?
5) Are there disadvantages to distributing a Runtime file instead of an ACCDE?

The sources I've found so far on Runtime are a bit confusing.
 

Cannot create ACCDE file

Preview
I receive the following error message when I try to create an .accde file. "Microsoft Office Access was unable to create the .accde, .mde, or .ade file." When I click on Show Help this is the message contained in it:

"This error is usually associated with compiling a large database into an MDE file. Because of the method used to compile the database, a considerable number of TableID references are created for each table. The Access database engine can only create a maximum of 2048 open TableIDs at one time. Exporting a database as an MDE potentially can exceed this limit if the database has a large number of objects (table, macro, form, report, etc).

There is no accurate method to estimate the number of TableIDs the Access database engine uses during the process of compiling a database as an MDE. However, each VBA module and each form uses one TableID, as a result, if the database has 500 forms, and each form's HasModule property is set to Yes, as many as 1,000 TableIDs are used."
From reading this, could the issue be that we have too many tables, forms, and queries existing in the database to be able to create the .accde file?
 

VBA Module(s) not available to ACCDE file

Preview
I saved my ACCDB file as an ACCDE for another version of my app. Previous versions of ACCDE work fine. This time, anything that requires VBA does not work. It's like VBA modules are not there.

When in the ACCDB version of the file, everything works fine. In the ACCDE everything is visible, including the Code Modules, of course they can't be opened as it's an ACCDE file. Everything works, except things that need VBA.

For example, one form loads fine, but a portion of it doesn't get populated because it's reliant on VBA. Command buttons don't respond, etc.

I can't think of anything I've changed since the creation of the last ACCDE that could cause this.