I am working on a medical database application (extensive patient
information/data) for physicians (4 physicians, 2 offices, 2 hospitals and
need to access from internet).
I know this is a broad question, but in terms of flexibility/power,etc,
does
Access 2003 have what I need or is SQL server what I should learn/use.
Also,
where does SQL Server Express fit into the equation. Is this going to
replace
Access?
Great question.
First, lets clear up a few things. When we talk about VB, or ms-access, we
don't usually refer to those tools as a "database". It is important to clear
up the fact that sql server can't create a form. It is important to clear up
that sql server express can't create a form.
So, when you talk about replacing ms-access with sql server, then what will
you use to write code with, and build forms with, and built reports with?
(sql server can't create reports, you can't build forms with code etc).
So, to loosely use sql server and interchange it with VB, or ms-access only
serves to "confuse" the issue here. Ms-access is a tool to development
software, built forms, and build reports. You can use ms-access with Oracle,
sql server, sql express, and of course the native engine called JET. So, one
of the things you are talking about is a software development tool, and the
other is the data engine you choose to use with ms-access.
You also have to remember that for the last 3 versions of access there has
been included a desktop edition of sql server (free) for use with ms-access.
So, SQL server express is going to replace that desktop edition that has
shipped with ms-access.
I am temped to fire back at you, and ask if you drop ms-access, then what
development tool(s) do you plan to make the application with? So, replacing
ms-access with SQL server, or sql server express is really not possible, and
they are VERY DIFFERENT tools. Ms-access is "far" closer to VB then it is to
sql server.
Now, you have commented, and talked about using the internet. Are you
talking about public users here?. Well, in that case, you don't need
ms-access, really can't use ms-access, and for all intensive purposes, you
will not even have to install ms-access on your web server. You can however
use the "JET" data engine with a web server (which is the native data engine
most of us use with ms-access). However, since for the LAST 3 versions
(going all the way back to a2000) you have a free database (server) engine
on the disk, then I see LITTLE if any reason to use the native "JET" engine
for a web server.
Take a quick read of the following notes of mine on how you setup ms-access
for multi-user:
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
After reading the above, you will understand the "split" concept. Now, for
Wide Area Networking (between two buildings for example), you can read the
following article of mine:
http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html
So, really, the sql server express is likely going to result in the MSDE
(sql desktop edition) going by the way side, and people choosing sql server
express in its place. I see little, if any effect on ms-access concerning
the issue of sql server express, and likely little if nay effect will occur
as result of this sql express product.
