Import database, tables, and relationships from MySQL 1

[realm174]

Hi guys,

I am trying to find a way to, I guess, export a database from MySQL and import it in Access. I don't really care for the data, as that can easily be recreated. But I would prefer to not have to re-create all the tables, indexes and relationships if at all possible. Google showed a few applications that can export the database structure from MySQL and save it in either sql statements, or XML format, but I have yet to be able to find a way that will do the whole deal.

It does not need to be an external application, but if it is, that's fine too.

Thanks!!



Cheers,

Realm174

 

[kjv1611]

If you've got multiple databases to deal with, then you'll have to have multiple databases in Access as well. The problem you're running into is that you're trying to squeaze a SQL Server setup into a way too small box. Whatever method you use to get it done, it won't be quick and easy - that's for sure.

 

[kjv1611]

If you've got multiple databases to deal with, then you'll have to have multiple databases in Access as well. The problem you're running into is that you're trying to squeeze a SQL Server setup into a way too small box. Whatever method you use to get it done, it won't be quick and easy - that's for sure.

 

[realm174]

It's actually one database with multiple tables (approx 20) with relationships between them.

The main reason for doing this, actually, is for deployment purposes. The application itself is quite small (in terms of filesize). The original idea was to distribute MySQL along with the application, or, alternatively, get the end user to download the MySQL msi package, for which I had created an "install" that would call and configure the msi to run with the application. Although this is working quite nicely, I realized that sending out an empty mdb file with the application would be a lot simpler. There is really not a whole lot that I cannot do with Access that would have otherwise required MySQL.

Hence the idea of switching over to Access instead.


Cheers,

Realm174

 

[kjv1611]

Well, obviously, you could just manually do it. 1 database and 20 tables doesn't sound like it would necessarily be all that bad. If you have time to take, you could manually do it, carefully, one step at a time..

I did find this software solution, but it aint cheap:

http://www.spectralcore.com/fullconvert/tutorials/convert-mysql-to-access.php

They do have a trial download that you could try just to see. If it's important enough, I imagine the cost would be worth it.

And actually, here's a MUCH cheaper program that supposedly does the same thing. It'd definitely be worth looking at, I think:

http://www.convert-in.com/sql2acc.htm

They have the standard version there that's good for converting one database... for $29. And I'd imagine it supposedly will handle the whole thing.

I've not tried either, but at $29 for a project that COULD end up being bigger than you expect, that price is not too shabby.

And of course, you may find another free alternative somewhere.. open source program..

And I imagine you could do some or most of it via VBA as well... but the time it would take would be probably worth more than $29, I'm guessing...

If you do give a program a try, I'd suggest starting with a copy of the database first to make sure it doesn't have risk of destroying your live database in the mean time.

 

[realm174]

http://www.convert-in.com/sql2acc.htm

did the trick, thank you so much!! Well worth the small cost.

Cheers,

Realm174