I have an appplication that reads information from Access Database, it uses ADO (msado15.dll) to open a database using Connection15::Open( ). I am unable to open Access 2007 database using this method. I get the following error: "Microsoft JET Database Engine, Unrecognized database format". Is there something I am doing wrong or I should be aware of? Does msado15.dll support Access 2007 databases? Thank you in advance.
I've been developing in Access 2002-2003, and now have Access 2007. I can open a 2002-3 .mdb database OK, but when I click on the Main Menu buttons, nothing happens -- they do not work. So I cannot access any of the existing Menus and Forms. In fact, none of the previously existing databases I tried will open/close Forms using the existing buttons. Any ideas?
There's possibly a very simple answer to this but it's been boggling my mind all morning and I can't find any answers on the net.
I'm opening a db on a network that was built with Access 2003. When I open it with Access 2003 on one pc it opens fine and I can edit it. But when I open it with Access 2007 I get a message saying that's it's opened the db in read only mode and that if I want to edit it I have to save a copy.
I tried opening the db exclusively but still no luck. Is there a reason why it's doing this and how do I get around it?
Using Access 2007, can I return a value for CurrentProject.FileFormat WITHOUT opening the database?
I'm looking for a way to determine the file version of a given Access database without actually "opening" the database in Access (I don't want it to ever be visible at all or in any way).
So to open a database in Access 2007 "without opening it," I'm using:
Code: Dim db As DAO.Database Set db = DBEngine.Workspaces(0).OpenDatabase("C:Path-ToFile.accdb")
From here, there are at least two different "version" indicators that can be used, as in this example:
Now, if you run this code on an Access 2002/2003 .MDB file, you will get:
Code: 4.0 09.50
If you run this code on an Access 2007 .ACCDB file, you get:
Code: 12.0 09.50
Note two important factors:The db.Properties("Version") seems to be returning the JET version from what I can see in research. This is NOT what I'm after.
The db.Properties("AccessVersion") returns THE SAME VALUE for an '07 ACCDB as it does for an '02-'03 MDB, since Microsoft never updated it, apparently.
Now.... the one way that I have found that ACCURATELY describes the version of a given access database file is to use:
Code: Debug.Print CurrentProject.FileFormat
...as this will always return, for example, 2.0 for an Access 2.0 .MDB file; 10 for an Access 2002/03 .MDB file; and 12 for and Access 2007 .ACCDB file (and there are others; these are AcFileFormat bitmask constants as described in Access support).
BUT, this CurrentProject object doesn't seem to be available (so far as I can see) when using the "open without opening" method described above.
SO, is there any way to return the FileFormat value without opening the database visibly? (Merely basing it in the extension isn't right either.... that would be easy but not accurate as several formats use MDB.
On trying to import an Excel 2007 file into Access 2007 I get the following:
1) Choose "External Data," Import, Exce 2) Select small file in MS Excel 2007 format. 3) Click on Import the source data into a new table ... 4) Choose OK
Immediately get "Microsoft Office Access has stopped working. Windows is checking for a solution to the problem..." This message never resolves, so I have to click 'Cancel'.
Then I get "Microsoft Office Access is trying to recover your information..." I have to click "Cancel" here as well and then kill MS Access in Task Manager.
Event Viewer gives following message, which is of no help: "ID: 2, Application Name: Microsoft Office Access, Application Version: 12.0.6211.1000, Microsoft Office Version: 12.0.6215.1000. This session lasted 710 seconds with 120 seconds of active time. This session ended with a crash."
Trying to import a small Excel 2003 file leads the same result. The same happens with a CSV file.
I have uninstalled and reinstalled Office 2007 as well. I am using Vista Ultimate.
I installed Office Enterprise 2007. Then I installed DEveloper Exrtensions, then Access Runtime 2007. All appear to have installed OK - they appear in Program and Features. Instructions on runtime packaging tell me that a Developer option should appear in the resulting drop-down when I click the Office button (top-left round thing) when I have a d/b open in Access. It's not there! I have un-installed and re-installed the extensions and the runtime - still nothing! Help! I do have Runtime 2002 (XP) on the same PC, is that relevant?
I am very close to completing a DB Program.... How can I create a desktop Icon that will Launch my Program without Loading Microsoft Access along with it???
I have installed Microsoft Access 2003 and Microsoft Access 2003 Developer Extensions. I can create Access application by using the Package Wizard. But after I upgrade from Microsoft Access 2003 to Microsoft Access 2007. I can't use the Package Wizard.
Attached is a screenshot of the relationships in a database I built a couple of years ago. It's worked absolutely fine in Access 2003 and currently has over 18,000 customers with associated information in it.
However, when I open the database in Access 2007 the performance is awful. All the forms are very slow to respond when tabbing between form elements. I've experimented by reducing the number of form elements calling on related data on a given page and whilst this improves performance it reduces usability - something I don't want to compromise on especially since Access 2007 should be able to cope with this.
My next question is therefore whether I've got the most efficient underlying table design and I can't see any other way of doing it than my current method so I'd be grateful for any feedback or advice anyone has.
Background Info: I developed our main department's Access 2003 split database which is on a server for 15+ Users. I've now been given Access 2007 for development -- Users still have 2003. There are also 2 other smaller databases that are not split (.mdb).
Problem: In the split database, I've saved the Application .mdb as 2003, relinked and made a new .mde. But the Users still cannot open the database. (I did this in a copy until I figure out the nuances with 2007.) The 2 other unsplit databases can be saved as 2003 version and Users can open OK.
I'm grateful for any suggestions on working with Access 2007. I've been trying to tackle the ribbon which is a whole other question.
Having a problem here after installing 2007. All my previously created databases work fine in 2007 (after clicking the enable, which is a pain,but don't know any other way) When I return to 2002 and try to open the databases I get different errors all something like this on....... "The expression On Open you entered as the event property setting produced the following error: Object or class does not support the set of events. Whats up here?????I have found a site here...http://allenbrowne.com/bug-17.htmlMentions this problem,but refers to Vista..... Does the same apply to XP? And which is the best fix?
I have an Access 2000/2003 database which opens up and displays correctly in Access 2007, but when I go to use the File>Print command, or for that matter any of the other pull down menu's nothing happens?
Has anyone else experienced thisproblem, or does anyone know what I am doing wrong?
I have created a database in Access 2007 that now works well, and one that I'm quite proud off. However, I can easily convert it to an Access 2000 format as can anyone else here, but when I load it up there is a major problem.
I have used the tab control in my main form and that has three tabs on it. However, it's positioned correctly in Access 2007 it's not positioned correctly in Access 2000 as I have to move the tab control down a bit, but that would seem fine. So I lowered the tab control form and changed my form layout slightly, but even then the tab control over all over the Access 2000 form whenever I interact with the tabs - most bizzare.
I have a database (.mdb file) which includes a table, forms and VB code. I intend on putting it onto a CD and then opening the form on another computer which may not have Access. Is this possible? Can I convert the file or can I attach some type of reader to the disk? I have seen some software for download on the internet which allows you to open the tables however the Form is the most important thing in this case (but I take it whatever I use, it will need to be able to view the VB, subforms and tables as well since the Form depends on them?).
...also can I install an auto-run to the file for when the disk is inserted? (this is not a major issue though).
I recently heard that Access 2007 ( part of MS Office 2007) can be purchased as a stand alone program. This sort of confirms that : look at pricing breakdown on : http://techrepublic.com.com/5254-6257-0.html?forumID=99&threadID=174062&messageID=1961442&id=3053951
I have downloaded Access 2007 trial, but I don't know how to use some of its features. When I try to open any of my databases saved as A2000, it displays a security message. "Security Warning: Certain content in the database has been disabled"
Hi, I have downloaded the access 2007 trial. Installed and registered it with the trial code. However when I try to install any of the free sample dbs from MS including the northwind db, Access crashes!! I was going to purchase the full version of office, but wanted to test access first. If anyone knows a solution, or can email the northwind 2007 db it would be appreciated.Many ThanksP.S. Screen dump of error is included.
I read this article from Allen Browne http://allenbrowne.com/Access2007.html#Bugs Has anyone had any problems with 2007, data, tables, etc. Our company would like to install, but after reading this, just second guessing myself. We have not yet installed the SP1. The company is gang ho about running with 2007.
I would like to hear your oppinion about new MS Access Jet db engine
I've been working with MS Access still 10 years, since version 2.0. I used to use MS Accesss for companies size of 10 pc users, and for any bigger company, I used MS Access as front end and MS SQL Server as back-end.
I bought recently MS Office 2007, with MS Access 2007. Before that, I read in one computer journal, that new, Access db Engine is completely made from scratch. And that this new engine is so good, that there are no needs to work with , for example MS SQL 2005 express. Also, I read, that during development phase of MS OFfice 2007, Microsoft development teams SQL Server and MS Access in Redmond, USA, fought among themselves, about is there need for Jet db engine, or not.
Engineers working in MS SQL development team, made a pressure on Microsoft board, to remove Jet engine from Access, as you can take MS SQL express for free, but on the other hand, MS Access dev. team, replied that new Jet is robust at least as MS SQL express 2005.
So, my question is: what do you think about it, is new Jet db engine, really so good and robust in MS ACcess 2007 ?