List:General Discussion« Previous MessageNext Message »
From:Nicholas Stuart Date:August 28 2002 11:15pm
Subject:Re: MS Access and mySQL
View as plain text  
Aye Arthur this is a different experince then what I had with Access and
MySQL. I guess my main reason for not using is because I personally dont
really need to. Nothing against you or anyone using it but to me it always
seemed to be a bit cumbersum, just my feelings.

I wish I had some e-mails I've seen about the downside of using Access for
a front end (I know I've seen some, but can't find em). I know this topic
has been discussed before. But if it works for you great!

And for your previous e-mail about the queries you are right that a lot of
them will work if you leave them in access, but if you plan on taking them
out then a lot of them may need some fine tunning for MySQL. Again,
whatever works for you.

My interpratation from Jon's original e-mail was that he had VB Forms and
the like in access (using vba) and was planning on moving those out of it
perhaps I was wrong. But if I read it right then my original feelings
still stand that you should not go through access to get to mysql from a
program. That would be kinda silly if you asked me, but thats besides the
point.

Glad you came along and pointed out another side Arthur. I guess it all
comes down to what you find works for you as there are A LOT of options
out there with no real "correct" way.

-Nick

p.s. Why is this needed:
>adding a column of type TimeStamp to every table in
>the database. This is necessary so that you can read auto-increment
>values.

Just curious  :)



> That has not been my experience, in fact my experience has been
completely
> the opposite. As my first test case I ported the Northwind sample
database
> to MySQL. I had to make a few changes here and there, most notably to
some
> queries, but also including (and I forgot to mention this in my previous
> reply on this subject) adding a column of type TimeStamp to every table
in
> the database. This is necessary so that you can read auto-increment
values.
>
> Next, I took my current app, with about 94 tables, and ported it. The
> production app is in MS SQL 2000, but I wanted to port it because I
wanted a
> proof-of-concept to show management. The absence of sprocs was a big
problem
> (come on, 4.1 :-) but I worked around it. No one but me and a few
testers is
> using this version. The production app remains in MS SQL.
>
> Finally, I took my killer-database, whose tables number 400+.
Fortunately,
> with dbScripter in hand I didn't have to create say 1000 indexes by
hand! It
> ported well and my Access front end talks blissfully to it. The MySQL
part
> resides on a P233 running Mandrake, set up for InnoDB. This may simply
be
> high praise for MyODBC, but my Access app has no difficulty at all
talking
> to the database.
>
> Arthur
>
> ----- Original Message -----
> From: <peter.brawley@stripped>
> To: "Arthur Fuller" <artful@stripped>
> Sent: Wednesday, August 28, 2002 1:57 PM
> Subject: [Fwd: RE: MS Access and mySQL]
>
>
>> wodya think?
>>
>>
>> -------- Original Message --------
>> From: "Nicholas Stuart" <nick@stripped>
>> Subject: RE: MS Access and mySQL
>> To: <bhester@stripped>
>> CC: <jonathanrcoleman@stripped>, <mysql@stripped>
>>
>> I would strongly urg you not to use Access as the front end. The
> biggest
>> problem is that the Jet Engine/Access backend is pretty much completly
>> different then MySQL and you will run into problems with table
> structure
>> and the like. Also, using access as the front end has been extremly
> slow
>> when ever I tried it.
>> You will however need to download the MyODBC driver if you wish to
> access
>> MySQL through VB.
>>
>> -Nick
>>
>> >
>> > -----BEGIN PGP SIGNED MESSAGE-----
>> > Hash: SHA1
>> >
>> > Jonathan,
>> >
>> > If you are going to be completely converting the Access db to MySQL,
>> > and just using Access as the frontend, you will need to download
>> > MyODBC:
>> >
>> > http://www.mysql.com/downloads/api-myodbc.html
>> >
>> > You can download either the stable or development release. There is
>> > also a FAQ that will answer your questions there about how to setup
>> > almost exactly what you are referring to.
>> >
>> > http://www.mysql.com/products/myodbc/faq_toc.html
>> >
>> > This FAQ is for the development release (3.51.03) but can also be
>> > used for the stable release (2.50.xx). I recently had to do the same
>> > thing with a Paradox database for a client, and have had relatively
>> > few issues following the documentation. After downloading and
>> > installing MyODBC you will be able to export the database directly
> to
>> > your Linux MySQL, however you will lose your table structures for
> the
>> > most part and will have to do some ALTER TABLE statements to put
> your
>> > keys back and the majority of your fields set to their proper type.
>> >
>> > HTH,
>> > Bryant Hester
>> > Juxtapose, inc.
>> >
>> > - -----Original Message-----
>> > From: Jonathan Coleman [mailto:jonathanrcoleman@stripped]
>> > Sent: Wednesday, August 28, 2002 12:40 AM
>> > To: mysql@stripped
>> > Subject: MS Access and mySQL
>> >
>> >
>> > Hi.
>> >
>> > I have a situation where a church I am doing some volunteer work for
>> > has a MS Access (office 97) database running on NT.  They are
>> > (woohoo) upgrading to a QUBE (linux box) for a server which has
> mySQL
>> > installed (and I can upgrade it etc..)
>> >
>> > My job therefore is to
>> >
>> > a) port MS Access data and queries to mySQL database
>> >
>> > b) use the MS Access forms to access the data and queries through
>> > ODBC.
>> >
>> > Is there anyone who can point me in the right direction, either to
>> > where the searchable discussion archives are, OR even better,
> someone
>> > who has gone through this before?
>> >
>> > Cheers
>> > Jon
>> >
>> > http://digital.yahoo.com.au - Yahoo! Digital How To
>> > - - Get the best out of your PC!
>> >
>> > -
> ---------------------------------------------------------------------
>> > Before posting, please check:
>> >    http://www.mysql.com/manual.php   (the manual)
>> >    http://lists.mysql.com/           (the list archive)
>> >
>> > To request this thread, e-mail <mysql-thread118159@stripped>
>> > To unsubscribe, e-mail
>> > <mysql-unsubscribe-bhester=juxtaposeinc.com@stripped>
>> > Trouble unsubscribing? Try:
>> > http://lists.mysql.com/php/unsubscribe.php
>> >
>> > -----BEGIN PGP SIGNATURE-----
>> > Version: PGPfreeware 7.0.3 for non-commercial use
> <http://www.pgp.com>
>> >
>> > iQA/AwUBPWzH6UlWu7/HFp4nEQJOGwCgr5af7wIi1AcbpP1rih/vABg/zb8An13w
>> > 4Tm8I6eugdNnVhLYZ+CcTYq2
>> > =Z0ov
>> > -----END PGP SIGNATURE-----
>> >
>> >
>> > ---------------------------------------------------------------------
>> > Before posting, please check:
>> >    http://www.mysql.com/manual.php   (the manual)
>> >    http://lists.mysql.com/           (the list archive)
>> >
>> > To request this thread, e-mail <mysql-thread118202@stripped>
>> > To unsubscribe, e-mail
>> <mysql-unsubscribe-nick=newtsplace.com@stripped>
>> > Trouble unsubscribing? Try:
> http://lists.mysql.com/php/unsubscribe.php
>> >
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> Before posting, please check:
>>    http://www.mysql.com/manual.php   (the manual)
>>    http://lists.mysql.com/           (the list archive)
>>
>> To request this thread, e-mail <mysql-thread118231@stripped>
>> To unsubscribe, e-mail
> <mysql-unsubscribe-peter.brawley=artfulsoftware.com@stripped>
>> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>



Thread
MS Access and mySQLJonathan Coleman28 Aug
  • RE: MS Access and mySQLBryant Hester28 Aug
    • RE: MS Access and mySQLNicholas Stuart28 Aug
      • RE: MS Access and mySQLRoger Davis28 Aug
        • RE: MS Access and mySQLNicholas Stuart28 Aug
        • Re: MS Access and mySQLGelu Gogancea28 Aug
  • mysql password ( )Mark Stringham28 Aug
    • Re: mysql password ( )lbelen28 Aug
    • Re: mysql password ( )Daniel Kiss29 Aug
  • Re: mysql password ( )Randy Johnson29 Aug
Re: MS Access and mySQLNicholas Stuart28 Aug
  • RE: MS Access and mySQLMary Stickney28 Aug
    • Re: MS Access and mySQLMark Matthews28 Aug
      • RE: MS Access and mySQLMary Stickney28 Aug
        • Re: RE: MS Access and mySQLEgor Egorov29 Aug
Re: MS Access and mySQLArthur Fuller28 Aug
  • Re: MS Access and mySQLNicholas Stuart29 Aug
Re: mysql password ( )Daniel Kiss29 Aug