GUI Interface for MySQL 2

[asimasm]

Hi
I m new to my SQL. Ihave been using SQL Server and MS Access in the past. Can any one tell me if My SQL has a graphical interface like MS SQL server and MS Access. Whcih would allow me to visually manipulate database objects and also desighn queries/views visually.

Thanks
Asim

 

[LittleSmudge]

given what you say ( NOW ) then

Create links to each external database
Links to the source db can be normal access linked tables

Link the MySQL via ODBC - but still as a linked table

Then you just need standard INSERT INTO queries and you just run them from code as
DoCmd.RunSQL "INSERT INTO tblTarget SELECT * FROM tblSource"


Try it that way and time it

THEN try using

DoCMD.RunSQL "INSERT INTO tblTarget SELECT * FROM tblSource IN RemoteDb"

and see if that affects the speed - I'd be interested in the result.

The second option uses the In database to get at the source data in a remote table and used a linked table via ODBC to Insert into the target.



'ope-that-'elps.



G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.

 

[Edski]

Thanks smudge,
I'll try the timer tests and report back in a few days. I'm interested too in the results since I have many tables with the biggest one containing over 6 million records!

Meanwhile...

To make the most of the Client-Server structure you DO NOT link tables from MySQL to the access front end via ODBC.

I'm still interested in this statement. My linked tables to MySQL were working fine and so were my parameter queries (using VBA) to transfer the data into them. Then I read this statement and thought perhaps I needed to rethink my project design. I realise that I cannot save a pass-through query (or normal query for that matter) that has paramenters in it. So my question still is: "Can I run a pass-though parameter action query in VBA on a MySQL table that isn't linked to any Access database? And if so, how"?

 

[LittleSmudge]

Okay - I'm sorry for the confusion.

The quote is inappropriate in the context of what I now understand you are trying to do.

IF you were considering the issue of opening a form and displaying a record from your table on the form THEN the quote is applicable.

But writing to the MySQL table in the way you describe - forget the comment.



Go back to my previous post and try the two DoCmd.RunSQL options aimed at a linked table via ODBC.






G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.

 

[Edski]

Thanks smudge.
Actually, I can do all that and it works fine but I was just worried that I might be doing it the wrong way. I feel better now.

About my query, I think I now realise that to transfer data to a MySQL table from an Access table requires the table to be linked first. This means I can't use a SPT query because I want to use INSERT INTO linked_tbl (IN dbs) SELECT * FROM local_tbl. Stupid really that I couldn't figire it out myself. I know now that there are applications available that convert Access tables to MySQL on the market. I'll definitely use a SPT query to read the data back from MySQL.

Anyway, I did some timing tests on using remote Access databases versus local ones and found absolutely no difference in speed.

Thanks again for your input.

 

[LittleSmudge]

INSERT INTO linked_tbl (IN dbs) SELECT * FROM local_tbl.

Once you have LINKED to the remote table Access can deal with it in exactly the same way as it deals with local tables. Therefore, if your MySQL table is linked then you don't need the IN dbs part. Linking does away with the need for all that.



'ope-that-'elps.



G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.

 

[perrymans]

* for LittleSmudge for giving me hope!

I thought I had to use PHP or Perl for my front-end development with MySQL because MySQL doesn't support ADO (as does SQL Server and Oracle).

Someone asked earlier for a book on using Access for a front-end, and I will repeat the request of a book or tutorial. I have browsed MySQL books before, bu they deal mostly with PHP and Perl development.

Thanks. Sean.

 

[LittleSmudge]

MySQL doesn't support ADO

MySQL supports ODBC

ADO can interface to ODBC

MSAccess 2000 can use ADO

Therefore MSAccess 2000 can be used as a GUI to MySQL



In the lines above you can replace MySQL with SQLServer, Oracle, FoxPro, etc and it still holds true.
As far as I'm aware it's just the same approach.


However, I'm not aware of any book on the subject of using MSAccess as the GUI for MySQL specifically.


What'd ya think, a slot in the market I could corner ?
Know any good ghost writers ?




G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.