How can I do this? Is it possible with no pain? I got nothing specific when I ask Google and search on SO. I have seen this post too but not sure that it comparable with my case.
An Access 2003 ADP project should work ok with Access 2007 or 2010. It won't work with 2013 or newer, though -- you will need to make a new .accdb database and link to the SQL data, then import the forms, reports & modules into the new .accdb file.
Related
Im in the process of porting a MS Access 2003 application to MS VB 6.0
Consequently, there are a few reports in there, which I need to port too.
Now I haven't found anything in formtypes or google, but is it possible to make something very similar to MS Access reports as a form in MS VB 6.0 or, even better, directly import a form from a MS Access 2003 .mdb file?
Mind you though, whatever I'll come up with, needs to work on everything from win95 to win10
You can try building on the included DataReport, but it isn't quite up to snuff with the ease of report generation you're familiar with in Access. The only time I had a budget, I used ActiveReports, but I don't even know if you can get that anymore, as they were bought out and are now selling a .Net version.
Is it possible for Access 2007 to open Access 2010 databases? My problem is at work we use Access 2007 but I need to edit the database at home where I use Access 2010. After I edit and save in Access 2010 and I open the database with Access 2007, I get the error "Unrecognized Database Format"... Please advise.
Thanks!
As far as I know in theory 2007 and 2010 should use the same format. But in real life they are different! One problem might be the references in VBA (VBA Windows, Tools, References). If you take a database from a computer with Access 2007 and work on the database in Access 2010 then some of these references are automatically updated to the newer office version (i.e. Microsoft Office 14.0 Access database engine Object Library). And when you try to use this database in Access 2007 again it won’t work because the references are changed. You can easily fix this by changing the reference back to what it was in 2007. I.e. change “Microsoft Office 14.0 Access …” back to “Microsoft Office 13.0 Access …” on the PC with Access 2007. Then at least that problem is solved. This is one of the problems between 2007 and 2010 but there are others which IMHO sometimes matter and sometimes don’t create a problem.
I has a headache, my question is not pure programming question, I don't know is it belong to the Stackoverflow question. Or it belong to somewhere else such as SuperUser?
Current System :
Currently, we are using Windows XP + Access 2003, we have a database system written in Access 2003 MDB format, it separtated into 2 MDB files, one for database data, and one for front-end.
Lucky, The front-end do not contain Data Access Page. It contains:
Forms, Reports, Queries, Macros, VBA Modules.
We have not use any third party objects, all forms/report only use the default Microsoft controls, all VBA only use the default Microsoft libraries.
My headache background :
Due to the policy of my company computer support department, force all of our computer workstation to upgrade from Windows XP + Office 2003 to Windows 7 + Office 2010, they force us to upgrade because they will not support old system.
My headache :
Now I study what should I do if my system will be Windows 7 + Access 2010. I have study something by Google. Here is my summary so far:
Solution 1 : Convert the front-end MDB to ACCDB, keep the back-end MDB.
Since back-end data is important, I don't want to take risk to do conversion. I am very concern will the front-end converion safe and easy? and can I link the ACCDB to MDB(password protected)?
Solution 2 : Convert both 2 MDB to ACCDB.
Will it easy and data safe? I worry it will crash my data.
Solution 3 : Keep both 2 MDB remain MDB
I read from Microsoft site, 97 MDB cannot change design, ok my system is 2003 MDB, but I very doubtful on 2003 MDB will have problems too. Access 2010 introduce many new objects, on the others hand, maybe some 2003 objects is no longer work in 2010. I have read from Google, some people cannot save the form/report design in MDB, because 2010 silently add the new objects.
Would anyone give me suggestion and share experience?
You have the option to keep your database in mdb and run it in Access 2010. In 80% of the cases it will run well with any change. If you have issues, there is a page:
http://allenbrowne.com/Access2007.html
and also a utility tool to test your database:
http://allenbrowne.com/AppIssueChecker.html
Take a look at both and you will see how you can solve your dilemma.
I apologize for this amateur question: this is my first experience with MSaccess.
When I try to start access 2010 by double-clicking my client's custdb.mdb, access 2010 complains:
Unrecognized database format 'custdb.mdb'
My client says only that "yeah, access 2010 is a problem."
Has anyone any idea what the problem might be and how I can fix it?
Alternatively, can anyone point me to a spot where I can download an earlier version of access, like maybe access2007. The MS download page insists I download Access2010.
Thanks!
I've always used MDB viewer for this purpose (http://www.alexnolan.net/software/mdb_viewer_plus.htm)
I then copy the data from that into MS Access 2010. It's a pretty horrible solution but it was the best I could come up with at the time!
This is probably a Jet 3 database. You can see that by opening the file with a hex viewer. Access 2010 doesn't handle Jet 3.
I'm hoping someone can either tell me what I'm doing wrong correct my flawed understanding of how this works and explain why it's not possible.
I've been developing a fairly basic database/program for a client in Access. They have Office 2007, I have Office 2010. Initial test of creating a database in 2010 (in "2007" format) and opening the forms and data in Office 2007 showed no problems.
Fast forward 3 weeks. I've sent them a recent copy for approval and they can't open it. Unrecognised database format. Upon looking around, it seems Access 2007 format doesn't really mean anything in terms of backward compatibility (thanks M$). I COULD follow the seemingly standard answer and remove empty fields, calculated columns etc but really don't think it should be necessary.
I've installed the Access 2010 runtime on one of the target systems with the understanding that it would allow me to open the Access 2010-developed ACCBD. No luck. Office 2007 still launches, and "unrecognised database format".
Is the problem that Access 2007 is installed on the target system? Or am I perhaps misunderstanding what the Access runtime distribution is for? Basically, is there a way to still deploy a program/database developed in Access 2010 without a) installing (and purchasing about 60 licenses of) Office 2007, or b) stripping back the existing ACCDB.
I haven't worked enough with A2007 and A2010 to help with the problem of A2007 not being able to open the ACCDB in which you were working in with A2010. Your understanding of how the Access runtime is for is basically correct.
However when the client was executing the A2010 runtime against your ACCDB did they create a shortcut referencing the path to the A2010 runtime msaccess.exe and the path and file name of the ACCDB? Similar to
"C:\Program Files\Microsoft Office\OFFICE14\ART\MSACCESS.EXE" "Q:\1 access\NewsgroupAnswers.mdb"
You can save in 2007 format from 2010 but one little known issue is that when you make changes in a 2007 access file within 2010 you will not be able to open it in 2007 again. To fix this you must create a -new- 2007 file and import all items into the fresh one (just compact and repair will not work) and then this new file should be usable within 2007 once more.