How do i set ms access 2007 database in crystal report - ms-access

I am trying to design a report in crystal report.
I have ms access 2007 as my database.
I started with new blank report file in crystal report. I thought creating new database connection using oledb but can find options for mdb files only but not the accdb file.
how can i get connected crystal report with access 2007 db
Edit:
I created new report.
1.) Clicked on Database Expert
2.) Clicked on Create New Connection
3.) Dbl Clicked on OLE DB (ADO)
4.) Choosed Microsoft Office 12.0 Access Database Engine OLEDB Provider
5.) Manually Copied .accdb file path from windows explorer and pasted it on Data Source
6.) Clicked on Next and Finish.
And finally it worked...
Is that fine? instead of copying file path manually isn't there a way to specify the path with browse functionality as in others?


There are a bunch of database access DLLs that you can choose to install when you install crystal, you may want to check that you have the correct database access files installed.
It maybe depreciated by MS but I find using the ODBC drivers works better with older file types. (I'm sure some one will tell me off for recommending this, but I guessing its not a mission critical report you are looking at)
Cheers
B


This is the standard method for linking to Access databases: Database Expert->Create New Connection->Access/Excel (DAO)
Have you already tried this method?


done that been there. It is getting harder with 2007 especially with Chrystal reports.
1)
Make a shell msaccess app tthat links to be databases
look into the north wind database same and figure out how to relink databases
In Chrystal reports use ODBC to link to the shell database.
Chrystal reports is getting difficult to use as it no longer supports Active X instead it use .net. I did get it work with Msaccess 2007-2010. but have issues with Access
2013

Related

Where to find Microsoft Access 2003? [duplicate]

I have an Access database created more than 10 yrs back.
I have very important data in it & I think it can be opened in Access 2007 or earlier version. Currently I have Access 2013 in my desktop and opening the file with this version results in the error "Cannot open a database created with a previous version of your application"
What is the solution for this issue? Is there any place where I can download the earlier version of MS Access?

I've just used Excel 2016 to open Access 2003 tables.
Open a new worksheet
Go to Data tab
Click on "From Access" menu item
Select the database's .mdb file
In the "Data Link Properties" box that opens, switch to the "Provider" tab
Select the "Microsoft Jet 4.0 OLE DB Provider"
Click on Next
Reselect the database's .mdb file (it forgets it when you change Provider)
Click OK
From the Select Table dialogue that appears, choose the table you want to import.

You can use MDB Viewer Plus from http://www.alexnolan.net/software/mdb_viewer_plus.htm to view or edit your old version database

As noted in another answer, the official word from Microsoft is to open an Access 97 file in Access 2003 and upgrade it to a newer file format. Unfortunately, from now on many people will have difficulty getting their hands on a legitimate copy of Access 2003 (or any other version prior to Access 2013, or whatever the latest version happens to be).
In that case, a possible workaround would be to
install a 32-bit version of SQL Server Express Edition, and then
have the SQL Server import utility use Jet* ODBC to import the tables into SQL Server.
I just tried that with a 32-bit version of SQL Server 2008 R2 Express Edition and it worked for me. Access 2013 adamantly refused to have anything to do with the Access 97 file, but SQL Server imported the tables without complaint.
At that point you could import the tables from SQL Server into an Access 2013 database. Or, if your goal was simply to get the data out of the Access 97 file then you could continue to work with it in SQL Server, or move it to some other platform, or whatever.
*Important: The import needs to be done using the older Jet ODBC driver ...
Microsoft Access Driver (*.mdb)
... which ships with Windows but is only available to 32-bit applications. The Access 2013 version of the newer Access Database Engine ("ACE") ODBC driver ...
Microsoft Access Driver (*.mdb, *.accdb)
also refuses to read Access 97 files (with the same error message cited in the question).

Non-Programming Answer: Download and install an older version of the Access Database Engine (2010 or 2007 for example, rather than 2013). Open Excel, navigate to the "Data" tab on the Ribbon and click "From Access". Import the data into Excel, and then Export to an accdb file or do whatever with it. NOTE! opening Access 2013 will trigger a re-install of the 2013 engine, so keep the 2007/2010 installation .exe around.
Programming Answer: Having installed an older version of Access Database Engine, you can use an OLEDB connection in multiple programming environments (C#, VBA, VBScript, etc.) to read/write and move Access data. Gord Thompson's answer also presents the option of jumping to SQL server and back.
See This post for a similar problem using an OLEDB connection
Connectionstrings.com is a great resource
See this post for how to setup an OLEDB connection using C#

You can do all these things but the underlying problem will be incompatibility with Windows updates of library files. Eventually you will have problems again. .ocx and .dll files will be clobbered and replaced: your database will not be able to cope with the new versions and it will not build or it will malfunction unexpectedly.

Instal Microsoft 2007 Access Runtime.
from https://www.microsoft.com/en-US/download/details.aspx?id=4438

Google Drive has an extension to open MDB files.
I'm not sure how well BLOBs work because I couldn't get my images to display but all the text came up.

NO, it does NOT work in Access 2013, only 2007/2010. There is no way to really convert an MDB to ACCDB in Access 2013.

If you're just seeking to pull the data out of tables contained in the mdb, use Excel and ODBC (DATA tab...Get External Data...From Other Sources...From Data Connection Wizard...Other/Advanced...Microsoft Jet X.X OLE DB Provider...pick your db...pick your table(s) and voila! Data imported. Then just save the workbook that then can be linked or imported into the newer version of Access to build a new database.

Dbeaver can open older Access .mdb and read Tables and Views. The ER diagram doesn't show the relationships though. However at least the table contents are easily extracted. It uses the UCanAcess driver, which if you say yes is automatically downloaded and installed when you first try and connect to an .mdb.
Note: Use "File >> Database >> New Database Connection" and not "File >> Open", else it just passes to the installed Access version and you'll get the same cannot open previous version error.
Here's a rediscovered mdb I opened today from cdrom not seen since 1999:

For a '97 Database...
Open the Access 97 database in Access 2003.
On the Tools menu, click Database Utilities, click Convert Database,
and then click to Access 2002-2003 file format.
Enter a name for the database, and then click Save.
Exit Access 2003.
Open the database in Access 2013.
On the File tab, click Save As, select Access Database (*.accdb),
and then click Save As. In the Save As dialog box, click Save.
All other versions:
To convert an Access 2000 or Access 2002 - 2003 database (.mdb) to the .accdb file format, you must first open the database by using Access 2007, Access 2010, or Access 2013, and then save it in the .accdb file format.
Click File, and then click Open.
Click the Access 2000 or Access 2002 - 2003 database (.mdb) that you
want to convert.
NOTE If the Database Enhancement dialog box appears, the database is using a file format that is earlier than Access 2000. To continue, see the section Convert an Access 97 database to the .accdb format.
Click File, click Save As, and then click Save Database As.
Choose the Access file type, and then click Save As.
If any database objects are open when you click Save As, Access prompts you to close them prior to creating the copy. Click Yes to make Access close the objects, or click No to cancel the entire process. If needed, Access will also prompt you to save any changes.
In the Save As dialog box, type a file name in the File name box,
and then click Save.
Access creates the copy of the database, and then opens the copy. Access automatically closes the original database.
Right from MS Office Documentation

In case you just need to dump the data you can use this clever script
http://youaccess.sourceforge.net . In case you are under linux / wine
you can try my procedure

Best solution would be to convert existing databases BEFORE upgrading to newer version/s of Access. Surely Microsoft should be warning users about this problem when upgrades are about to be installed.

To convert the data to a MySQL database, you can use the Bullzip Access to MySQL program. It's free and easy to use.
http://www.bullzip.com/products/a2m/info.php

Running MS Access VB Module from ArcCatalog

I created some VBA code that runs a make table query in MS Access. Whenever the MS Access database is opened it automatically runs the SQL and updates the table.
I then created a database connection in Arcatalog to the MS Access database where I can link to the MS Access .accdb file and add the table to ArcMap.
When I have items linked in ArcMap with the db connection I get the .laccdb extension along with the .accdb extension. I was hoping that since arcatalog was linked to the access database that this would trigger the VBA code and re-run the code and update the linked table in ArcMap without having to go into the Access database each time.
I noticed that in the VBA editor window I can click on some ESRI references.
Is there any line of code that I can add that will make the access database run once it is initialized by ArcCatalog via the database connection that I have set up utilizing any of these ESRI references libraries that I see in MS Access?
thanks

ODBC connection report for Crystal Report not working on other machines

SETUP
I am currently running on Crystal Report 2011.
I have created a Crystal Report that pulls data from a MySql database. I had to setup an ODBC connection in the Data Source wizard under Admin Tools. I created the report and saved it. I then opened it up in a report view and it worked fine.
PROBLEM
When i try to run the report on another computer, it gives "Failed to open a Connection". I setup the ODBC connection on the other computer.
QUESTION
Does anyone know how to make it so i can deploy a Crystal Report using MySql tables to other machines?

Based on your original question, it sounded like you had trouble accessing a MYSQL db from a different node (server), and my suggestion was to make sure that user and node were entered into MySQL's user table. I happen to use the grant directive to do this.
MySQL's access is user/ip-address based, whereas MS SQL Server is either server login (sa or other users) or Windows domain login based. Although an Microsoft SQL Server expert would call these two login approaches using more correct terminology, these approaches are slightly different than MySQL's approach.

MS access mdb file has a "repair" status first time it is opened from Access 2007

I have created an .mdb file programatically from another .mdb file using VBScript. It creates a table in the second .mdb file and populates data. Everything works fine and data is populated correctly. This is done using JET 4.0 driver.
The issue is that when I try to open the .mdb file using Access 2007, it tries to repair the file first. I do not know why that is happening. If I try to open it in Access 2003, it opens without the repair. I need to fix this. Has anyone run into this before or any ideas as to why it is happening?

Are you sure it's the mdb that needs to be repaired? Or is it the windows installer loading up and trying to repair MS Access?
MSAccess has some issues running multiple versions on one machine, look for "Windows Installer messages in Access" on this page. The repair process is controlled by various registry entries you may be able to create a process to reset these and prevent the repair process running.

Error migrating from Access 2007 database to 64-bit SQL Server 2008

I am using 64-bit Vista and I need to migrate an access database, in Office 2007 to SQL Server.
I don't want to have to write an SSIS package to do this, but that may be my only option.
Is there any other way to do this? I have about 330M of data in Access that needs to be moved, so I can write a webapp to replace this database.
Update: The error is:
The upsizing Wizard does not work with the version of Microsoft SQL Server to which your Access project is connected. See the Microsoft Office Update Web site for the latest information and downloads.

In Access, use the upsizing wizard under tools menu...
Edit, checked to see if it's still there: it has issues with SQL Server 2008.
Do you get the same error? (yes you do, says your edit)
Alternative: SSMS/Migration for Microsoft Access

See if creating a Linked Table inside Access DB (which points to your destination table in SQL Server) helps.
OR
See if you can use SQL Server functions (such as OPENROWSET) to open the Access tables.

The SQL Server 2008 Import/Export tool has worked great for me for migrating tables as well as data. You may need to install the SQL Management Studio to get the import tool also (it'll show up in your Start menu). It supports moving tables/data around from various sources, and I'm guessing that Access 2007 is supported.
That said, the SSMS/Migration for Microsoft Access tool may work the best overall.
Best of luck.

When all else fails, you could try creating an ODBC DSN for your SQL Server and then export the tables to that DSN. It won't get all the datatypes right, but it might be good enough to get things started if nothing else works.
I think it's pretty amazing that you can export a Jet/ACE table to an ODBC data source, to be honest.