On Tue, 5 Oct 2010 23:56:28 -0700 (PDT), The Frog
<mr.frog.to.you (AT) googlemail (DOT) com> wrote:

Absolutely. I'd be happy to post a link on my blog. I would suggest
adding a created/modified date so folks can see how current it is a
few years from now.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

Hi there once again,

Sorry for the delay in my reply. I have had issues with posting to
this newsgroup. Short summary for you: The comparison 'report' is in
production. There is actually quite a lot of information to organise
and compare and comments to be made. It is a little larger a project
than I gave it credit for. Later today I will have a new corporate
laptop, so I will do fresh installs of both db servers and do some
basic performance comparisons and provide the code for these in the
report. Please bare with me as I write this - I saw it going more
quickly in my mind.........

I will do a walkthrough document for setting up MySQL on Ubuntu Server
and working with Ms Access after I have completed the first. I will
also try and include here a walkthrough of sorts for migrating from
Access as BE to MySQL as BE with the Pentaho Data Integration tool
(PDI). I hope you can bare with me while I put all this together.
Mostly at the moment it lives in my head and my chicken scratchings in
my desk drawer.

Cheers

The Frog

The Frog <mr.frog.to.you (AT) googlemail (DOT) com> wrote in
news:d8052006-b2b5-44a0-9378-bfbcfe101184 (AT) e14g2000yqe (DOT) googlegroups.co
m:

Is this in addition to a comparison of the free versions of MySQL
and SQL Server? To me, a pay version of MySQL, or needing to buy
products to migrate to it easily makes it inferior to the pay
version of SQL Server.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

No need to pay anything. I use PDI simply because I like it. Its kind
of like having a swiss army knife for manipulating data. I will only
be working with the Community / Express versions of the databases, and
this applies to any tools that I might use with them. The goal here is
to try and provide a non costed set of tools to be able to work with
for projects that require more than FE / BE access can reasonably
handle.

What I wont be touching is paid for versions of any of the products,
or specialised versions or scenarios such as replication and
clustering, slave servers etc.... This is meant to be a comparison of
doing a straight out BE swap-out with an Access FE. I think that
unless I limit the writeup to this I will be scribbling away for
months with all the possible permutations, possibly even longer! I am
just going to try and keep it simple and clean, written in plain
English, and diagrams everywhere I can to provide as much clarity as
possible - you would still need to be database savvy to understand the
content though as I wont be explaining things like normalisation and
table design etc... I am taking this background understanding for
granted - ie/ you have worked with and / or designed DB's and apps in
Access before. I think thats a reasonable place to start.

I should be done with the MySQL setup and the SQL Server 2008 R2
Express setup today (my time, I'm in Germany). Maybe tomorrow if the
BE migration takes longer than I expect. I must say, although slightly
off topic, this new laptop rocks! Core i5 520M, very nice indeed.

The Frog

SQL Server developers edition is $49 you fucking retard

only by moving to SQL Server and using Access Data Projects- can you avoid complexity.

Access 2000-2003
File, New, Project (new database)