this makes the error go away but it doesn't work in the access query bulder. I reall yam looking for something that works in both access and sql server
Main Topics
Browse All TopicsI'm trying to move my back end database from access to sql server 2005 and am really just learning sql server. I am getting the following error for the sql statement below. I imagine it has something to do with how sql server deals with null values.
As I am still in the testing phase and still have the live version in access if possible I would like to find a solution that works in both access and sql server.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
ms access's and sql server's fucntions to deal with null values are different (no surprise there, eh?).
in order to be able to use the same function in sql server as you do in ms access, you will have to create such a function in sql server yourself.
a good solution would be to use NZ() ms access function in your queries - it uses same syntax as sql server's isnull() function - and create a corresponding NZ() function in your sql server.
here's a link to sample code for creating NZ() function in sql server:
http://www.databasejournal
hth
Azadi
> To put it mildly it ain't going to happen.
+1.
While there are many similarities in syntax, they are two totally different beasts. Trying to get 100%
compatibility is near impossible for anything beyond very basic statements.
Besides, MS SQL is much more powerful than Access. Trying to code to Access's standards means
you may be creating less efficient queries, which kind of defeats the purpose of using a more powerful
database in the first place.
OK, I'm convinced they are 2 different beasts and we should look at them differently. It would have been 'nice' in this transition phase to have a common solution...but in the end I will have much more control with sql server.
I'm sure I'll be posting more questions as I make my way through the access >> sql server transition.
thanks for all the iinput.
Business Accounts
Answer for Membership
by: AanvikPosted on 2009-04-27 at 16:03:52ID: 24246505
Select allOpen in new window