Jet or SQL

  • Thread starter Thread starter DS
  • Start date Start date
DS said:
Where do you change your engines? I want to change from Jet to SQL....?
Thanks
DS
Click to expand...

Hum, I got a Honda, and I want a Toyota engine!! ;-)

Not to split hairs, but ms-access is thoroughly based on sql, uses sql for
forms, reports, combo boxes, and just about everywhere else.

So, ms-access by its very nature is a sql product, and built around sql.

So, I think you mean you want to change from the JET engine to use sql
server.

You can't change from "JET" to sql, as JET is a sql product!!

You can also use Oracle, MySql, Sysbase, PostGres and a good number of other
database systems with ms-access.

So, we are talking about going from a "file based", or so called "file
share" mdb file for the back end to a server based product.

However, you do realize that sql server, or oracle (or whatever server based
system you choose) as a general rule requites its own box, and MORE
resources to run. Further, you will need the skills, and expertise to
administer, setup, and run that server based system.

So, assuming you got the skills to run, setup, and administer sql server,
the using this server based system with ms-access is easy.

Lets assume for the time being we are talking about Microsoft's sql server
(it is not clear which database system you intended to use with ms-access,
so, we will pick the most common server based system).

When you choose to use sql server with ms-access, you can keep your existing
mdb file, and LINK the tables to sql server. This approach is preferred when
you got a existing application, as then not too much code need be changed.

If you are new to sql server, and don't really know a lot about setting up
sql server, then you can use what is called a ms-access ADP project. This is
a special kind of ms-access application that is designed 100% specially for
use with sql server. The advantage of a ADP is that when you create a table,
you get to use the familiar query builder, and table builder, and the
resulting tables and queries are created on the database server you are
connected to. The disadvantage of a ADP project is that none of your dao
code for a existing mdb file will work. So, if you got a large complex
existing mdb application, then linked tables are a better choice then adp.

However, to play, test, and try things with sql server, then a ADP project
is likely the way to go.

So, if you want to switch to sql server, then it is assumed that you have
sql server installed on a server system. There is also a lightweight edition
of sql server included on the office CD (has shipped with access for the
last 3 versions - starting with access 2000 to the now 2003 version).

Since your original question seems a bit vague, then it is not clear if you
are familiar with sql server, and you really do need to be to use it with
ms-access.

It is also not clear if you are looking to use ms-access in a multi-user
situation, or need sql server for reasons of connections to the data?

If you only need a few users in the 5-10 range, then often just sticking
with ms-access is fine, but you do need to split your database. You can read
about splitting here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

Further, if you have not been running a split database now, then trying to
jump to sql server might be a bit too large of a jump for you.
 
Albert said:
Hum, I got a Honda, and I want a Toyota engine!! ;-)

Not to split hairs, but ms-access is thoroughly based on sql, uses sql for
forms, reports, combo boxes, and just about everywhere else.

So, ms-access by its very nature is a sql product, and built around sql.

So, I think you mean you want to change from the JET engine to use sql
server.

You can't change from "JET" to sql, as JET is a sql product!!

You can also use Oracle, MySql, Sysbase, PostGres and a good number of other
database systems with ms-access.

So, we are talking about going from a "file based", or so called "file
share" mdb file for the back end to a server based product.

However, you do realize that sql server, or oracle (or whatever server based
system you choose) as a general rule requites its own box, and MORE
resources to run. Further, you will need the skills, and expertise to
administer, setup, and run that server based system.

So, assuming you got the skills to run, setup, and administer sql server,
the using this server based system with ms-access is easy.

Lets assume for the time being we are talking about Microsoft's sql server
(it is not clear which database system you intended to use with ms-access,
so, we will pick the most common server based system).

When you choose to use sql server with ms-access, you can keep your existing
mdb file, and LINK the tables to sql server. This approach is preferred when
you got a existing application, as then not too much code need be changed.

If you are new to sql server, and don't really know a lot about setting up
sql server, then you can use what is called a ms-access ADP project. This is
a special kind of ms-access application that is designed 100% specially for
use with sql server. The advantage of a ADP is that when you create a table,
you get to use the familiar query builder, and table builder, and the
resulting tables and queries are created on the database server you are
connected to. The disadvantage of a ADP project is that none of your dao
code for a existing mdb file will work. So, if you got a large complex
existing mdb application, then linked tables are a better choice then adp.

However, to play, test, and try things with sql server, then a ADP project
is likely the way to go.

So, if you want to switch to sql server, then it is assumed that you have
sql server installed on a server system. There is also a lightweight edition
of sql server included on the office CD (has shipped with access for the
last 3 versions - starting with access 2000 to the now 2003 version).

Since your original question seems a bit vague, then it is not clear if you
are familiar with sql server, and you really do need to be to use it with
ms-access.

It is also not clear if you are looking to use ms-access in a multi-user
situation, or need sql server for reasons of connections to the data?

If you only need a few users in the 5-10 range, then often just sticking
with ms-access is fine, but you do need to split your database. You can read
about splitting here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

Further, if you have not been running a split database now, then trying to
jump to sql server might be a bit too large of a jump for you.
Click to expand...
Thanks Albert...It sounds like a Jump, but something that I might want
to do in the future, Thank youfor the clarification, greatly appreciated.
DS
 
Back
Top