Syntactical difference b/w MS Access and MS SQL Server

[PriyankaVerma]

i need to develop a client-server application in which access is used at the backend on the client side whereas the server uses MS SQL Server.
here i have a problem, do the two DBMS have any syntatical difference issues. help???

 

[r937]

yes they do, although i wouldn't call them "issues" because they are just differences that you have to know, that's all (and if you don't know them, the database engine gives you nice error messages)

example: sql server uses CASE, access uses IIF

rudy

 

[SemperFiDownUnda]

"i need to develop a client-server application in which access is used at the backend on the client side whereas the server uses MS SQL Server."

Do you mean you have a client server application that needs to store some information locally?

My first statement is that Microsoft® Access is not a database engine. It is a front end to a database engine. With Microsoft® Access 2000 you can choice this to be either JET or MSDE (which is a SQL Server engine and uses the exact same T-SQL syntax as its full server sibling)

If you give more information on what you are trying to achieve perhaps we can give you some sound advice on the architectural design of your application.

But in Short I would say use MSDE on the client side and then you over come many problem like data corruption that could occur on client side due to hardware or software failures.

 

[jrbarnett]

SemperFiDownUnda's suggestion to use MSDE is a good one. MSDE is a cut down version of SQL Server.

I would add though that MSDE also exists in Office XP/2002.

What you don't get with MSDE that you do get with the full SQL Server is the full set of administration tools, but you gain the ability to run it on Win98, NT 4 Workstation, 2000 Pro and XP whereas SQL server proper is strictly NT server and 2000 server only. Only the admin tools can be run from a workstation, you can't host the actual database engine on it.

John