[AccessD] MySQL be and Access FE

For Access management you might try FMS Agent.

http://www.fmsinc.com/Products/Agent/index.html

Bob Heygood



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Nancy Lytle
Sent: Sunday, July 27, 2003 5:07 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] MySQL be and Access FE


I guess I miss worded it a bit.  What I mean is that with MSDE or MySQL you
can have all the databases under one umbrella, ie the Management console or
with MySQL you have a choices of some management tools such as MySQL Control
Center, NaviCat (PremiumSoft MySQL Studio, etc, so that I can, in one place,
set up backups data imports etc.  The actual databases are all separate and
will remain separate.  I guess I am just tired of running around the network
to do the administrative parts of my job.  And since there isn't really any
comparable tool for Access, that's why my thougts went to MySQL, although I
guess MSDE would be an option.
Hope this makes more sense,
Nancy


William Hindman <wdhindman at bellsouth.net> said:

> Nancy
>
> ....you didn't say why you are not considering consolidating them into mdb
or
> MSDE (free SQLServer) bes rather than MySQL ones ...while there are
> pros/cons to using MySQL as the be, if consolidation is your only issue
and
> you have a choice of be, then an Access be would normally be my first
> choice, an MSDE my second if speed or data criticality justified it and
the
> user numbers were small, and MySQL only if neither of the first two
worked.
>
> William Hindman
> ....It's a proven fact that if you smoke a pack of cigarettes a day for 90
> years, you'll live to a ripe old age. :)))
> ----- Original Message -----
> From: "Nancy Lytle" <nancy.lytle at auatac.com>
> To: <accessd at databaseadvisors.com>
> Sent: Sunday, July 27, 2003 6:37 PM
> Subject: [AccessD] MySQL be and Access FE
>
>
> > I have inherited multiple databases, and the number is growing. The
> databases
> > are small but contain import information (important, not mission
> critical). I
> > am splitting those that are not already split and using FE Autoupdater.
> My
> > problem At this point is that the databases are all over the network
> making
> > it harder to administer.  I have no say at this point in where the
> databases
> > are located.  I would like to get everything consolidated so I can more
> > easily handle backups, checking data integrity, etc.  The best way I can
> see
> > to do this would be to use MySQL for the BEs and Access for the front
end.
> > This way I will have all the data in one location that will be easy(ier)
> to
> > administer and I can concentrate on the front ends.
> > Does this sound like a plan? (I am choosing MySQL for its price - we do
> not
> > need the additional capabilities of SQL Server for these databases).
> > Any other suggestions welcome.
> > TIA
> >
> >
> > --
> > Nancy Lytle
> > EIS
> > nancy.lytle at auatac.com
> >
> >
> > _______________________________________________
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
>
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>



--
Nancy Lytle
EIS
nancy.lytle at auatac.com


_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com