(Another) "unable to create accde" in Access 2007
https://www.experts-exchange.com/questions/27625383/Deploy-as-ACCDE.html
Greetings all ...
I can't seem to get around the failure to create an ACCDE file. I've run through the steps outlined in the above link's question 4 times, and feel I'm doing everything to the letter.
This is a huge conversion for a project I've had available for years, but only as a linked ACCDB FE/BE pairing. It's important enough that I be able to create these ACCDE files that I'm trying to make sure these larger functions will work before I invest another 30 or 40 hours in development time.
There are about 25 linked tables (no data, just structure), and 2 forms. I have a reference out to a Lib Db, existing in the same folder as the file I'm trying to convert. I'm trying to convert it into the same folder as the source ACCDB file.
The only thing I can think of that's weird is that I made the mistake of letting the wizards create the 5 command buttons on one of the forms, before realizing that it creates those little embedded macros. Each of my command buttons has ancillary behaviors built in, so I went in and "replaced" (I think ... I don't know how to delete these little macros) the Click event reference with a regular section of code in the class module. I've compiled, repaired, decompiled , recompiled, repaired, compiled, decompiled and repaired so many time now that I can't imagine there are still vestiges of those original little embedded macros, but what do I know?
All I know is that Access is throwing up the "Unable to create Accde" dialog box almost as fast as I select a location for the file, and I can't get beyond it. And I need to know if this whole conversion to an accde will be an unachievable goal before I get to much further.
I understand this question has been covered before, but let's just call this a "Hail Mary".
Many thanks in advance for any suggestions as to what I might look for (in addition what MX covered in the above link)
All best,
John
Greetings all ...
I can't seem to get around the failure to create an ACCDE file. I've run through the steps outlined in the above link's question 4 times, and feel I'm doing everything to the letter.
This is a huge conversion for a project I've had available for years, but only as a linked ACCDB FE/BE pairing. It's important enough that I be able to create these ACCDE files that I'm trying to make sure these larger functions will work before I invest another 30 or 40 hours in development time.
There are about 25 linked tables (no data, just structure), and 2 forms. I have a reference out to a Lib Db, existing in the same folder as the file I'm trying to convert. I'm trying to convert it into the same folder as the source ACCDB file.
The only thing I can think of that's weird is that I made the mistake of letting the wizards create the 5 command buttons on one of the forms, before realizing that it creates those little embedded macros. Each of my command buttons has ancillary behaviors built in, so I went in and "replaced" (I think ... I don't know how to delete these little macros) the Click event reference with a regular section of code in the class module. I've compiled, repaired, decompiled , recompiled, repaired, compiled, decompiled and repaired so many time now that I can't imagine there are still vestiges of those original little embedded macros, but what do I know?
All I know is that Access is throwing up the "Unable to create Accde" dialog box almost as fast as I select a location for the file, and I can't get beyond it. And I need to know if this whole conversion to an accde will be an unachievable goal before I get to much further.
I understand this question has been covered before, but let's just call this a "Hail Mary".
Many thanks in advance for any suggestions as to what I might look for (in addition what MX covered in the above link)
All best,
John
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ok, but before you proceed make sure you have the latest service pack (SP3) for office 2007
To find what SP you have
Office Button > Access Options > Resources
Look in the About section
http://www.microsoft.com/download/en/details.aspx?id=27838
To find what SP you have
Office Button > Access Options > Resources
Look in the About section
http://www.microsoft.com/download/en/details.aspx?id=27838
ASKER
OK. That didn't take long.
I can't convert a file with a VBA reference to an external database. There are no module calls, no objects to speak of in either file. Just the mere existence of a reference to an external database seems to be what's ticking off the poor little delinquent.
Certainly changes the nature of my question.
Do you know if that means that option is off the table for good?
I'll noodle with the few approaches, and will probably rephrase a new question tomorrow, given that we can narrow down the problem somewhat.
Thanks again for your help in nudging me into "experiment and error trap" mode. The more I work with Access the more it seems I really should always be ready to adopt that approach.
Best,
John
I can't convert a file with a VBA reference to an external database. There are no module calls, no objects to speak of in either file. Just the mere existence of a reference to an external database seems to be what's ticking off the poor little delinquent.
Certainly changes the nature of my question.
Do you know if that means that option is off the table for good?
I'll noodle with the few approaches, and will probably rephrase a new question tomorrow, given that we can narrow down the problem somewhat.
Thanks again for your help in nudging me into "experiment and error trap" mode. The more I work with Access the more it seems I really should always be ready to adopt that approach.
Best,
John
ASKER
And yes, I do have SP3 installed. Release 12.0.6606...
John
John
ASKER
The points are yours for responding, my friend.
On the bright side, your recommendation (to remove certain objects and try again) did lead me to the further revelation regarding the external reference, and the revised question.
All best...
John
On the bright side, your recommendation (to remove certain objects and try again) did lead me to the further revelation regarding the external reference, and the revised question.
All best...
John
John,
sorry, i was not able to post back yesterday got very busy..(easter sunday)
anyway, i saw that you posted another q regarding external library.. and i will leave it to jdetmann to sort this out for you (you are in good hands)
sorry, i was not able to post back yesterday got very busy..(easter sunday)
anyway, i saw that you posted another q regarding external library.. and i will leave it to jdetmann to sort this out for you (you are in good hands)
ASKER
I deleted links to all the tables except one (still no data, just structure), deleted all the forms, (which presumably eliminated the class modules), eliminated all the code from the Main module (but left the module itself in place, with the single Option Explicit line), and eliminated all the macros. I then compiled, exited, restarted, repaired, exited, restarted, decompiled, exited, restarted, repaired again, exited, restarted and compiled again (didn't need to this time, because the Compile option was greyed out). The system threw up the dialog box indicating it failed to create the ACCDE file as soon as I hit the enter key after selecting a file location (No real surprise this time on the speed of the dialog box feedback, given that there was nothing left in the file to convert in the first place...)
So I'm unable to convert a file with nothing in it but a good link to an empty table and a module with a single line.
Thanks for your feedback, my friend. But clearly I am not meant to be able to convert this app to an accde file.
And yes, I know I know I know. Next, I'll cold boot my workstation 5 or 6 times and then create a brand new file, just for this exercise. I won't set any external references, or create any forms, macros, queries or tables. I'll create a single module, with the two words "Option Explicit". And I'll see what happens when I try to convert that file. If it works, I'll begin adding objects back in, one at a time, attempting to reconvert into a new ACCDE file after creating each command button and after saving each new line of code, until it fails and tells me where it hurts.
Sheesh. We'll see what happens.
Please excuse my not well hidden frustration. I do very much appreciate your response. I'll post a followup note in a day or so to document the results.
Thanks again, and all best.
John