[AccessD] Re: Access with a MySQL database

Barb,

That is what I figured.  The only thing you need to
watch out for when creating recordsets in code is
in the db.openrecordset.  On the end of it, you
need to add dbseechanges.  If you will change
the queries to views as you can, you will also get
better performance.  But, essentially, you can
almost do nothing to the front-end and make the
change over to SQL Server.

Robert

At 04:55 AM 10/28/2004 -0500, you wrote:
>Date: Wed, 27 Oct 2004 14:49:10 -0400
>From: "Barbara Ryan" <BarbaraRyan at cox.net>
>Subject: Re: [AccessD] Re: Access with a MySQL database
>To: "Access Developers discussion and problem solving"
>         <accessd at databaseadvisors.com>
>Message-ID: <002101c4bc55$a5ac6fc0$0a00a8c0 at cx470148a>
>Content-Type: text/plain;       charset="iso-8859-1"
>
>That's good news (regarding Microsoft SQL) --- they currently are using
>Access 97, but are converting to XP in the near future, so looks like
>they'll have it.   I don't think that they will have more than 10 users.
>
>Barb
>
>
>----- Original Message -----
>From: "Robert L. Stewart" <rl_stewart at highstream.net>
>To: <accessd at databaseadvisors.com>
>Cc: <martyconnelly at shaw.ca>
>Sent: Wednesday, October 27, 2004 2:20 PM
>Subject: [AccessD] Re: Access with a MySQL database
>
>
> > If they have Office 2000 or higher, they have SQL Server in the MSDE.
> > It is good for up to 10 concurrent users.
> >
> > My SQL does not support stored procedures, views, or referential
> > integrity.  SQL Server, even the MSDE, does.
> >
> > Robert