August 15, 2005 at 5:43 am
Hi
I have just changed from mdb to adp and now want to make an ade file for additional security.
I created an new adp file in Access 2003. When I came to use Database Utilities to convert to an ade file, it told me it was created in 2000 and needed to be converted to 2003 format. I was surprised, but, as I had imported a couple of forms (created in 2000) and amended the code, I thought that this might have caused the 'problem'.
So, I converted the db to 2003 format and tried again to create an ade file from it. It just gave the very helpful dialog: "Microsoft Office Access was unable to create an ade database".
I've been through Help - to no avail - I don't have references to other dbs either adps or mdbs.
I have tried creating a fresh adp and importing forms etc into it. Still no joy.
Has anybody any ideas how I might get over this problem.
Thanks
Paul
August 15, 2005 at 5:52 am
I'm not sure what the problem is, but:
Try creating a blank Ac2003 ADP file, setting the connection to your database using the built-in ADP connection manager.
Then import all of your database objects (except for the database tables!!!- they are already present from your new connection, and will be made into duplicate copies if you "import" them) into the new ADP file. Make sure you also import your CommandBars.
Then set up all of your options and startup options, as before.
Hopefully, you should now be able to create an ADE file from it.
HTH,
Rich
August 15, 2005 at 6:01 am
To make the ADE file from an ADP, you must connect to a SQL Server database. If not, you can not do that.
August 15, 2005 at 6:12 am
Hi Rich
I did try that, but have just gone through it again to check. I was just about to import one form and try a one by one test, however I noticed that the database window title bar already says "Access 2000 File Format". This is without doing any importing.
The tables I am using on the SQL Server are the original ones (holding all of my data) used with my mdb - with mostly new sps and views.
I'm not sure what is going on here?
Many thanks
Paul
August 15, 2005 at 3:24 pm
Ahah, I think I know the problem. I use Ac2002, but that should not matter. Go to Tools-->Options-->Advanced, and look at the setting for "Default File Format." If it says "Access 2000," then that is likely your problem (I think Ac2000 still may be the default in Ac2003!).
I have no idea what the difference is between the formats, but I would:
1) Open up a blank database and change the default format to 2003. I think the format only applies to new databases that you create AFTER you change the default format. Now close Access.
2) Open Access, and create a new Ac2003 ADP, and verify that the format for your new database is Ac2003. If it is Ac2003, then import all the objects into it. If this does not work, I'll try to think of something else.
HTH,
Rich
August 16, 2005 at 2:50 am
Hi,
This may be the problem,
Whenever i get that error message when trying to create an mde/ade file, the problem has always been caused by a compile error in the vba code. Make sure you recompile the code before creating an mde/ade file.
iano
August 16, 2005 at 7:57 am
Thanks Ian
I have compiled the code. I'm grateful for your contribution.
Thanks Rich
Another surprising find. Who would believe a new installation of 2003 would have 2000 as its default file format.
Anyway, I now have a fine young .ade.......
Very many thanks, once again
Paul
March 13, 2006 at 7:13 pm
Thank you!
August 10, 2006 at 2:25 pm
Another thanks!
September 24, 2007 at 5:45 pm
The only result that returned anything on Google while from searching for "Microsoft Office Access was unable to create an ADE database". Thanks - this pointed me in the right direction that with a little bit of finessing I could find a way to get my circumstances to work.
September 26, 2007 at 3:07 am
Hi Russell
I started this thread and became a big supporter of Access.adp. The ability to deal natively with SQL tables is fantastic. Access started as a little desktop database, but was grown enthusiastically by Microsoft. It really came of age for developers with .adps.
However, from v2007, Access appears to have reverted to a desktop tool. No more support for the native use of SQL tables. My enthusiasm for developing in Access has evaporated. I am looking to move to VS2005. It seems such a shame when a company 'pulls the plug' on such a great developers tool.
Best wishes
Paul
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy