Hi Graham,

On your date problem try code like this

insert into employees (firstname, lastname, birthdate) values('rick',
'dobson','9/9/1944')

As you migrate from Access to SQL Server, you will notice a wide series of
issues, such as differences in wildcard parameters, that are not covered by
the standard SQL Server literature.  In addition, there are other issues
that will be new to Access developers, such as stored procedures and
triggers.  In spite of these differences, Access can make a powerful
development tool for SQL Server solutions.  This is especially true if you
decide to use Access projects, which vastly simplify SQL Server development
from Access.

I wrote a whole book for professional developers who are migrating from
Access to SQL Server.  Its title is Professional SQL Server Development with
Access 2000.  This book especially targets those using SQL Server 7 and
MSDE.

If you are using SQL Server 2000, then I urge you to consider Access 2002 to
develop SQL Server solutions.  This is because Access 2000 requires a couple
of special patches to work with SQL Server 2000, but Access 2002 works with
SQL Server as it comes out of the box.  In addition, Access 2002 gives you
better control over SQL Server.  For example, you can create your own
user-defined functions in SQL Server.  My new book Programming Microsoft
Access Version 2002, which will be available in a couple of weeks, includes
two chapters (over 200 pages) on developing solutions for SQL Server 2000
with Access 2002.

Subject: SQL Server and ADO question (plus question for list moderator!)
From: "graham brown" <gbrown@c...>
Date: Fri, 3 Aug 2001 10:40:48 +0100
X-Message-Number: 1

Hi

I've just moved a web app from using ADO and Access to using SQL Server,
there are some code differences which I can't find out about.

I am using this line to create a recordset in ASP and it gives me an error
with upper
strSQL="select * from mytable where upper(myfield)='TESTING';"

The other problem is dates, what I have is this

strSQL="Insert into mytable (mydate) values (#01/08/01#);"

From what I can gather # denotes a variable and not a date like in access

I'd appreciate any pointers please!
Do Wrox have any books out which deal with programming with SQL Server and
ASP/.NET?

Rick Dobson
www.programmingmsaccess.com
www.cabinc.net
rickd@c... <mailto:rickd@c...>