That's all I know if everybody could explain the rest I would be grateful
Subscribe to HRA Now!
Are you a Google Analytics enthusiast?
Share and download Custom Google Analytics Reports, dashboards and advanced segments--for FREE!
www.CustomReportSharing.com
From the folks who brought you High Rankings!
More SEO Content
International SEM | Social Media | Search Friendly Design | SEO | Paid Search / PPC | Seminars | Forum Threads | Q&A | Copywriting | Keyword Research | Web Analytics / Conversions | Blogging | Dynamic Sites | Linking | SEO Services | Site Architecture | Search Engine Spam | Wrap-ups | Business Issues | HRA Questions | Online Courses
Sponsored Content
Microsoft Access 2003
Started by
tomsk
, Jan 19 2005 10:07 AM
7 replies to this topic
#1
tomsk
-
- Active Members
-
- 323 posts
HR 5
- Location:UK
Posted 19 January 2005 - 10:07 AM
I am looking to back up some information held in a database my understanding is that I must get the mysql to talk to my copy of microsoft access 2003.
That's all I know if everybody could explain the rest I would be grateful
That's all I know if everybody could explain the rest I would be grateful
#2
Raphael
-
- Active Members
-
- 722 posts
The Limey Cowboy
- Location:New England
Posted 19 January 2005 - 10:10 AM
Err, depends. I don't see any reason why you need to get the two DBs to talk to one another... Of course, I don't know the details of your operation =)
But each database should be able to be backed up fairly easily, and unless you have some very specific needs that I can't think of right now, I don't see why you'd want to back up one DB to another.
But each database should be able to be backed up fairly easily, and unless you have some very specific needs that I can't think of right now, I don't see why you'd want to back up one DB to another.
#3
Randy
-
- Moderator
-
- 17,540 posts
Convert Me!
Posted 19 January 2005 - 10:51 AM
You can use an open source application called phpMyAdmin to export the MySQL database tomsk. That's the easiest way to create a dump or backup of all of the data and database structure, though I'm not positive that it will put it into Access format for you. I know that it'll put it into a format that Excel (.csv) can read since that's what I use.
What type of server are you on? If it's a Windows IIS machine I would assume that they offer the ability to save databases in Access format since they're both Windows. But I don't know for sure since I don't run any IIS servers.
Is there any wisdom out there from IIS users?
What type of server are you on? If it's a Windows IIS machine I would assume that they offer the ability to save databases in Access format since they're both Windows. But I don't know for sure since I don't run any IIS servers.
Is there any wisdom out there from IIS users?
#4
tomsk
-
- Active Members
-
- 323 posts
HR 5
- Location:UK
Posted 19 January 2005 - 11:26 AM
QUOTE(Raphael @ Jan 19 2005, 11:10 AM)
But each database should be able to be backed up fairly easily, and unless you have some very specific needs that I can't think of right now, I don't see why you'd want to back up one DB to another.
Raphael at the moment the the database is stored on the server of the host so I need for my puposes to back it if anything went wrong.
#5
Raphael
-
- Active Members
-
- 722 posts
The Limey Cowboy
- Location:New England
Posted 19 January 2005 - 11:51 AM
No no, I totally understand why you need to back it up. What I don't understand is why you need to back up a MySQL database to an Access database.
Just back up the MySQL database using (as Randy suggested) something like phpMyAdmin..
I guess I don't see where the Access database comes into play.
When you back up a database, you do not need to transfer that information into another database. It can be backed up purely as files. (Which you can then restore the original database from, should circumstances require)
Just back up the MySQL database using (as Randy suggested) something like phpMyAdmin..
I guess I don't see where the Access database comes into play.
When you back up a database, you do not need to transfer that information into another database. It can be backed up purely as files. (Which you can then restore the original database from, should circumstances require)
#6
tomsk
-
- Active Members
-
- 323 posts
HR 5
- Location:UK
Posted 19 January 2005 - 12:27 PM
As well as backing up the database I was hoping to extract information from it, which I understood you could do with access 2003?
#7
Raphael
-
- Active Members
-
- 722 posts
The Limey Cowboy
- Location:New England
Posted 19 January 2005 - 12:45 PM
What information do you want to extract? You mean access the data held in the backed up database files?
Um.. I don't know if Access will read MySQL tables or not.
If you're backing up from a Linux server to a Win-based machine, I'd just install MySQL for windows on that machine and access the backed up tables that way. MySQL have some nifty free graphical tools for accessing and administrating a database now.
Um.. I don't know if Access will read MySQL tables or not.
If you're backing up from a Linux server to a Win-based machine, I'd just install MySQL for windows on that machine and access the backed up tables that way. MySQL have some nifty free graphical tools for accessing and administrating a database now.
#8
Ron Carnell
-
- Moderator
-
- 959 posts
HR 6
- Location:Michigan USA
Posted 19 January 2005 - 01:29 PM
QUOTE
I know that it'll put it into a format that Excel (.csv) can read since that's what I use.
Access reads CSV files just fine. There is the potential for some naming conflicts, though generally Access is less restrictive on naming tables and fields than is MySQL, but even those can easily be resolved while setting up the import (there's a Wizard to walk you through it).
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
