ACCDE conversion conflict with external library reference
Greetings all ...
I'm running into a conflict while trying to convert an Access 2007 accdb file to an accde file. Access persistently reports that it is "unable to create the accde ... file".
I've narrowed down the cause of the conflict to the mere existence of a VBA reference to an external library file in the file I'm trying to convert.
As an experiment, I created a new accdb fiile, named Db1. There is only one object in Db1, a main module with a single line reading "Option Compare Database". This file converts just fine to accde format.
I then create a second accdb file in the same folder, and name it Db2. Db2 contains no objects. I create a VBA reference to Db2 in the VBA window of Db1 under Tools/References.
When I then attempt to again convert Db1 to an accde file, Access fails, reporting it's "Unable to create the .accde ... file."
I've tried this with and without a module in Db2, and I've tried it converting Db2 to an accde file before creating the reference in Db1. All fail.
Does anyone have a solution to this, other than the obvious? I can't believe this is an illegal procedure. Am I missing a hidden configuration item in Db2 (or Db1) that will allow me to keep the reference to the shared library Db2 in Db1, and still convert Db1 to an accde file?
Many thanks for any thoughts you have on this matter. I greatly appreciate your efforts, expertise and perspective.
Best,
John
I'm running into a conflict while trying to convert an Access 2007 accdb file to an accde file. Access persistently reports that it is "unable to create the accde ... file".
I've narrowed down the cause of the conflict to the mere existence of a VBA reference to an external library file in the file I'm trying to convert.
As an experiment, I created a new accdb fiile, named Db1. There is only one object in Db1, a main module with a single line reading "Option Compare Database". This file converts just fine to accde format.
I then create a second accdb file in the same folder, and name it Db2. Db2 contains no objects. I create a VBA reference to Db2 in the VBA window of Db1 under Tools/References.
When I then attempt to again convert Db1 to an accde file, Access fails, reporting it's "Unable to create the .accde ... file."
I've tried this with and without a module in Db2, and I've tried it converting Db2 to an accde file before creating the reference in Db1. All fail.
Does anyone have a solution to this, other than the obvious? I can't believe this is an illegal procedure. Am I missing a hidden configuration item in Db2 (or Db1) that will allow me to keep the reference to the shared library Db2 in Db1, and still convert Db1 to an accde file?
Many thanks for any thoughts you have on this matter. I greatly appreciate your efforts, expertise and perspective.
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.
ASKER
Thanks, Jim ...
Just came on the site to report that I believed I had found a solution when I came across your response. It was good to find your confirming perspective.
My earlier failures to convert the "top level" file, after I had converted the "referenced" file to an accde format, must have been due to ancillary matters (perhaps I hadn't compiled Db1 again, after changing the reference from the accdb to the newly converted accde file).
In any event, you're right. The solution was a matter of starting out at the extremities and converting any 'daisy chained' support files, first. Once the files being referenced are all accde's, the top level file tipped just fine.
Many thanks for your articulate response. This one really had me going there for a while.
All best,
Jed
Just came on the site to report that I believed I had found a solution when I came across your response. It was good to find your confirming perspective.
My earlier failures to convert the "top level" file, after I had converted the "referenced" file to an accde format, must have been due to ancillary matters (perhaps I hadn't compiled Db1 again, after changing the reference from the accdb to the newly converted accde file).
In any event, you're right. The solution was a matter of starting out at the extremities and converting any 'daisy chained' support files, first. Once the files being referenced are all accde's, the top level file tipped just fine.
Many thanks for your articulate response. This one really had me going there for a while.
All best,
Jed
ASKER
Whoops. I should have awarded the points to your first response. I didn't have to decompile (at least this time around!) to solve my issue.
Although, I'm glad you mentioned the decompile option as a possible further requirement; it will likely come in handy for others who find this question.
Thanks again for your help!
Jed
Although, I'm glad you mentioned the decompile option as a possible further requirement; it will likely come in handy for others who find this question.
Thanks again for your help!
Jed
Decompile :-)
Just an FYI. If you are creating a 'DE' ... and you have a Reference set to one or more 'DBs', then *every* DB in the Reference food chain *must* also become a DE ... otherwise you will get that error message.
mx
Just an FYI. If you are creating a 'DE' ... and you have a Reference set to one or more 'DBs', then *every* DB in the Reference food chain *must* also become a DE ... otherwise you will get that error message.
mx
<<Does anyone have a solution to this, other than the obvious? I can't believe this is an illegal procedure. Am I missing a hidden configuration item in Db2 (or Db1) that will allow me to keep the reference to the shared library Db2 in Db1, and still convert Db1 to an accde file?>>
When your making a DB and it uses external libs, the sequence that you compile them in is critical.
First, open, compile and save the lib. If your converting it to a MDE, then do so now.
Then open your main app, uncheck the lib reference and close the DB. Now open, re-check the reference, and then compile.
Now you should be able to convert the main app to a MDE.
Jim.