Advice for a simple web-based database

[John Michl]

I have a short time need for three people in different locations to
share a simple database. I'm helping on an auction for my church and I
want the church secretary, the coordinator and myself to be able to add
information to this database from our computers via an internet
connection. The db would probably only have four or five tables
(donor, item, bidder, etc.) and at most a dozen fields per table. I'd
like to use a database so we can avoid e-mail Excel sheets to each
other and constantly consolidate them.

I have some experience creating simple Access databases and prefer to
use that tool since I'm familiar with creating tables, queries and
reports. However, I've never placed a database on a web site so I
don't know set it up and access it. I have a personal site hosted by
Go Daddy and I believe I can turn on database access for mySQL and
possibly MS Access.

Here are my questions:

Can I copy the access database to a folder on the site and then utilize
the forms and queries in the db as if it was on a local machine?

If I create the db in Access can I somehow synch it with a local copy?
On Auction night, I'll need to have the database on a laptop since I
won't have Internet access.

Are there simple ways to update a web-page for auction participants so
they can view the current list of donated items? (No editing, just
viewing.)

Any suggested resources that would help me get started? My web-master
experience is limited to creating a couple of relatively simple sites
with Frontpage (www.johnmichl.com and www.facetsbykathy.com). I have
no experience in languages such as PERL, ASP, etc. Very strong Excel
skills including VBA and some MS SQL and MS Access skills.

Thanks.

- John

 

[Albert D. Kallal]

Unfortunately, ms-access is not a web tool.

You could however connect the front end to your database server (in this
case mysql).

On the other hand, perhaps using remote desktop would be a possible solution
(especially if you have more then one machine on the same network as the
ms-access appcation).

I speak about using ms-access over a WAN here:
http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

 

[John Michl]

Thanks, Albert. Regarding your first suggestion (connecting to
MySQL)...I'm not sure how this is typically accomplished. Can I create
the database in Access and then somehow transfer it to my web-hosting
company into MySQL? I've never used MySQL so I don't know anything
about it.

Thanks.

- John

 

[Albert D. Kallal]

Thanks, Albert. Regarding your first suggestion (connecting to
MySQL)...I'm not sure how this is typically accomplished. Can I create
the database in Access and then somehow transfer it to my web-hosting
company into MySQL? I've never used MySQL so I don't know anything
about it.

Well, Sql server, or in this case MySql is just a database engine. You can
continue to write/develop/use your ms-access as the front end, and the data
is placed on the server. However, since you don't know anything about sql
servers, the you likely need to get up to speed on that technology (not
something you can do over night - so, if you plan to use a sql server of
some type you have to learn that system).

If you are pressed for time, and don't want to re-write, then your only real
choice is remote desktop. Terminal services (remote desktop) would requite
that you are running windows 2000, or 2003 *server* in your office (the
server edition allows two free remote users at the same time - after that,
you need to pay for licensing, and setup gets a little more complex).

So, you can transfer your *data* to sql server, or oracle, or MySql.
However, sql server, (or oracle, or mysql) does not have any ability to
build a user interface with. This why developers using VB6, or web
developers use sql server (as it holds the data, but you still have to write
the interface part). By the way, the same applies to ms-access. You can link
tables to sql server. So, c++, VB6, web developers, and yes even ms-access
developers write their appcation, but they place the data into sql server
(the data has to be placed somewhere!! -- The only really difference here is
that ms-access has a built in data engine, but you can well move the data
out into sql server, and *continue* to use ms-access. This would mean that
each user will need a copy of the front end instead on teach machine (means
they would need ms-access, or the very least the developers "runtime"
edition of ms-access if they did not want to purchase ms-access). With
remote desktop, (or a web based system), then the users would NOT have to
have, nor install ms-access on each machine.

So, sql server etc is typically used for web based applications - you write
the application side with your web tools + web site, and that application
pulls the data from the tables which resides in sql server. So, keep in mind
that most database systems (servers) do not provide the user interface, but
YOU have to built that interface with your favourite tools (be it ms-access,
or your favourite web development tools).

Conceptually, this means that if you were to *just* use the table design
part, and the table views directly, that is typically what you get with
oracle, or sql server (or mysql). You have NO forms design ability. So,
those tools typically let you setup the tables etc. You then have to choose
a set of tools to build the forms with (your web system, or vb6, or even
ms-access). If you use ms-access with sql server, you typically used linked
tables (hopefully you been using a split database..that helps you learn this
concept).