How Easy To Convert Access > MySQL?

[Helpless Soul]

Hi all.

I am not a novice, I am a total beginner!
I want to start a database on sports results. Ideally, I'd like this to
be MySQL/PHP/dynamic web-based. but I'm afraid that's beyond me at this
stage. So, my idea is to design the DB using Access, later importing
this to MySQL (getting someone to write the necessary php and web pages
for me).

My question is, is this feasible, is it simply a stupid idea...or...?

Thanks for your comments.

HS

PS. I have Access 2007 and the older version (Office XP). Which is
simplest/best to use?

 

[Helpless Soul]

Hi all.

I am not a novice, I am a total beginner!
I want to start a database on sports results. Ideally, I'd like this to
be MySQL/PHP/dynamic web-based. but I'm afraid that's beyond me at this
stage. So, my idea is to design the DB using Access, later importing
this to MySQL (getting someone to write the necessary php and web pages
for me).

My question is, is this feasible, is it simply a stupid idea...or...?

Thanks for your comments.

HS

PS. I have Access 2007 and the older version (Office XP). Which is
simplest/best to use?

Just a bit of an after-thought - maybe I should try and do it in Excel?
....so same question. How easy to later convert it to MySQL?

HS

 

[Albert D. Kallal]

Hi all.

I am not a novice, I am a total beginner!
I want to start a database on sports results. Ideally, I'd like this to be
MySQL/PHP/dynamic web-based. but I'm afraid that's beyond me at this
stage. So, my idea is to design the DB using Access, later importing this
to MySQL (getting someone to write the necessary php and web pages for
me).

My question is, is this feasible, is it simply a stupid idea...or...?

Thanks for your comments.

Keep in mind that MySql has no ability for you to design the report for the
user interface part, so you're not really using any part of MS access code,
forms, or report for development purposes when you go to convert this to a
web based application.

So you have to ask yourself what benefits due you gain by designing this
application in access, then redesign it all over again using some other web
based development tools?

Remember MySql does not let you build reports, write code, or build user
interface things like forms.

So if you choose MySql, then that's only going to be a place to store your
data, you'll still have to choose a set of development tools to build the
front end or user interface part of an application. You can build that front
in part in MS access. And, you can even have your front end part of
ms-access connect to the the database MySql.

On the other hand if you're planning for web based development system, MS
access is not going to help you one bit. What do you gain by building the
application in MS access, then having it completely redeveloped in some
other web based system?

So it's not a question is this is really feasible, it just that you don't
gain anything by building a form in MS access that cannot be used as a form
on your website. The only common thing that will be salvaged between the two
applications will be the data part, but all of the work and costs is going
to be building the user interface part of this application. So you really
gain nothing if you build a front end part in MS access with the intention
that it'll eventually be used as a web based application.

 

[Helpless Soul]

Keep in mind that MySql has no ability for you to design the report for the
user interface part, so you're not really using any part of MS access code,
forms, or report for development purposes when you go to convert this to a
web based application.

So you have to ask yourself what benefits due you gain by designing this
application in access, then redesign it all over again using some other web
based development tools?

Remember MySql does not let you build reports, write code, or build user
interface things like forms.

So if you choose MySql, then that's only going to be a place to store your
data, you'll still have to choose a set of development tools to build the
front end or user interface part of an application. You can build that front
in part in MS access. And, you can even have your front end part of
ms-access connect to the the database MySql.

On the other hand if you're planning for web based development system, MS
access is not going to help you one bit. What do you gain by building the
application in MS access, then having it completely redeveloped in some
other web based system?

So it's not a question is this is really feasible, it just that you don't
gain anything by building a form in MS access that cannot be used as a form
on your website. The only common thing that will be salvaged between the two
applications will be the data part, but all of the work and costs is going
to be building the user interface part of this application. So you really
gain nothing if you build a front end part in MS access with the intention
that it'll eventually be used as a web based application.

OK, thanks for your help.
The idea was that I have Access and it is local, not remote, as such I
find it easier to play with and save securely. I already know how to
make a table and enter records in Access, but have zero idea in MySQL.
Regarding Excel, I know how easy it is to import records from text or
csv files, and I was assuming Access is as easy. Again, I've no idea how
this would work with MySQL.
I guess what I am saying is that I could play with Access a lot more
easily than MySQL without the worry of losing data, how to enter new
records etc., and then later simply use a converting program (ESF?) to
import that into MySQL.

HS

 

[John W. Vinson]

The idea was that I have Access and it is local, not remote, as such I
find it easier to play with and save securely. I already know how to
make a table and enter records in Access, but have zero idea in MySQL.
Regarding Excel, I know how easy it is to import records from text or
csv files, and I was assuming Access is as easy. Again, I've no idea how
this would work with MySQL.
I guess what I am saying is that I could play with Access a lot more
easily than MySQL without the worry of losing data, how to enter new
records etc., and then later simply use a converting program (ESF?) to
import that into MySQL.

It's with some trepidation that I venture to disagree with Chris and Albert
but... I would expect that there would indeed be at least some benefit to
using Access as a testbed for your table structures. Creating tables in MySQL
requires running DDL (Data Definition Language) queries such as CREATE TABLE
zxy FIELDS(...), rather than MakeTable queries - but there are tools available
to generate just such table creation scripts from an Access database; you
could make sure your tables are correctly normalized and can handle the data
that you want; you can migrate the data from local Access tables to linked
MySQL tables; you may even want to keep an Access linked frontend to work with
the data along with your web frontend.

I do speak as someone familiar with Access, though, so it's a natural first
choice! YMMV....

 

[David W. Fenton]

east some benefit to
using Access as a testbed for your table structures. Creating
tables in MySQL requires running DDL

Er, no, it does not. You just install Apache, PHP and phpMyAdmin.
Anybody who can design tables in Access can design them in
phpMyAdmin.

 

[John W. Vinson]

Er, no, it does not. You just install Apache, PHP and phpMyAdmin.
Anybody who can design tables in Access can design them in
phpMyAdmin.

Thanks, David.... wasn't aware of those additional programs.

 

[a a r o n . k e m p f]

I agree-- PhpMyAdmin is a fantastic product.

but the bottom line is that MS SQL Server is a better free database
server than any flavor of mySql

I'd reccomend using Access data Projects to move from Jet to SQL
Server and then you're free to use MS SQL Server databases when and
where you need.

-Aaron

 

[David W. Fenton]

Thanks, David.... wasn't aware of those additional programs.

To be fair, you will be *executing* MySQL DDL, it will just be
phpMyAdmin that will be writing it for you.

It's a damned good web-based interface (though a few things are very
annoying). The good thing about it is that you you don't need to
write SQL to change your schema, nor know any of the options needed
to do so.

 

[James A. Fortune]

It's with some trepidation that I venture to disagree with Chris and Albert
but... I would expect that there would indeed be at least some benefit to
using Access as a testbed for your table structures. Creating tables in MySQL
requires running DDL (Data Definition Language) queries such as CREATE TABLE
zxy FIELDS(...), rather than MakeTable queries - but there are tools available
to generate just such table creation scripts from an Access database; you
could make sure your tables are correctly normalized and can handle the data
that you want; you can migrate the data from local Access tables to linked
MySQL tables; you may even want to keep an Access linked frontend to work with
the data along with your web frontend.

I do speak as someone familiar with Access, though, so it's a natural first
choice! YMMV....

I agree with John. If you're a novice, Access makes a great
cost-effective choice for showing what you want to accomplish. Also,
his idea of having Access linked to your MySQL data is a great benefit.
However, a good software developer doesn't require a running
application in order to see what you want. You can usually diagram out
what you want and then she will take care of normalization of the data
and the programming. You might just be wasting time by doing some of
the early programming yourself, except to understand well the value of
what programmers do.

James A. Fortune
(e-mail address removed)

 

[a a r o n . k e m p f]

of course, SQL Server is the same price, it is much faster, and it
doesn't have questionable legal future

 

[a a r o n . k e m p f]

and SQL Server has intellisense in SSMS. For SQL statements.

-Aaron

 

[Tony Toews [MVP]]

of course, SQL Server is the same price, it is much faster, and it
doesn't have questionable legal future

Please explain, in detail, what product has a questionable legal future.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[David W. Fenton]

"a a r o n . k e m p f @ g m a i l . c o m"


Please explain, in detail, what product has a questionable legal
future.

With citations to reputable websites.