"Sagi" <sa**@schieber.net> wrote in message
news:42******@news.bezeqint.net...
i'm building an aplication that in the end sopuse to run on SQL but i'm
building it on access.
do i am going to have alot of work when im going to change database?
When you say 'run on SQL' do you mean the Microsoft product 'SQL Server'?
The acronym SQL stands for Structure Query Language, which is the standard
language for manipulating relational databases, and is implemented by most
vendors of database products (to a greater or lesser extent).
As Larry correctly points out, there is a slightly limited version of SQL
Server called the MSDE available with Access. It's limitations, at least in
terms of data volume and user audience, wouldn't prevent you developing
effectively in it. Though as Larry says, the extra tools, especially
Enterprise Manager, that you get with the Developers Edition of SQL Server
are very useful (do you get BOL with the MSDE, anybody know?).
There are 2 halves (or more!) to a database application. The database engine
and the client interface. In an 'Access only' system the client interface
would be developed in Access and the database engine would be Jet, which is
the database engine that comes with Access, and which Access clients work
with very well. Access sometimes appear to be one product, but you need to
understand right from the start that it is really 2 products.
In a SQL Server system SQL Server is the database engine and the client that
you use to interact with the database is up to you. Access makes a good
client to SQL Server, or an application developed in VB, or whatever you
like. Many database web sites use SQL Server as the database, and the
'client' is a web application, a set of .asp pages.
If know for certain that this thing will use SQL Server as the database
engine when it goes into production then you would well advised to develop
it in SQL Server/MSDE.
Mike