SQL Server 2005 Express is a special edition of SQL Server 2005 that addresses the small business market.  SQL Server 2005 Express is fully compatible with SQL Server 2005.  However, SQL Server 2005 Express does not contain many of the enterprise features available in SQL Server 2005.

SQL Server 2005 Express interoperates particularly well with Visual Basic 2005 Express and Visual Web Developer 2005 Express.  Through November 7, 2007, all three packages are available without charge from Microsoft.  Therefore, they represent a compelling choice for organizations and individuals in search of free, quality software.  You can learn more about how to use SQL Server 2005 Express from:

As for Microsoft plans for a replacement, nobody knows for sure.  MSDE used to interoperate with reasonably well with Access.  However, MSDE has been replaced by SQL Server 2005 Express.  I have not noticed any "offiicial" comments from Microsoft about Access/SQL Server Express interoperability.  The Office team seems intent on re-designing the Access UI for end users as opposed to making Access/Jet developer-friendly.

Access is best for single-user and departmental solutions with 20 or fewer concurrent users. In addition, it is best if no individual table exceed several tens of thousands of rows. Overall, Access has a maximum database file size of 2 GB.

While Access is a file-server database manager, SQL Server is a client/server database manager. Microsoft also encourages the use of SQL Server in n-tier solutions.  SQL  Server is best for large departmental applications as well as enterprise solutions. Database sizes can reach to terabyte size and the SQL Server can accommodate many more concurrent users than with Access. Developing solutions for SQL Server typically requires more advanced skills. Therefore, unless you have advanced programming and database skills, you may find Access a friendlier development environment.

In addition, you can output XML from any ADO recordset. The format is a little obsolete, but it is XML. To write XML based on an ADO recordset use the Save method for the recordset object with an adPersistXML argument. My previous page reference illustrates the detailed syntax. The main advantage of this approach is that it does not require Access 2002 as does the ExportXML method.

USE master

DROP DATABASE databasename

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 date delimiters and 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.  Use Professional SQL Server Development with Access 2000 to learn about the differences and new features as well as how Access projects can expedite the creation of SQL Server solutions.

Second, if this solution does not work for any reason, consider using SQL-DMO to programmatically manage the remote server. As you may know, SQL-DMO is a COM object that you can reference from VB or even the VBE window of Access 2000/2002. After the reference, you can make a connection to a server and administer it programmatically. This approach is very flexible since you can expose just the functionality that you prefer.  I wrote a four-part series on this topic for SQL Server Magazine, and my upcoming book titled Programming Microsoft Access Version 2002 includes even more advanced coverage and samples on this topic.

First, you should understand that MSDE, the Microsoft Data Engine, ships with all versions of Office 2000 that include Access 2000. MSDE uses SQL Server technology. You program like you do SQL Server, but it is available for free as part of Office 2000. Therefore, if you have Access 2000, you have MSDE that you can use to learn about SQL Server.

The figure of 255 users is for the upper limit for the number of users over a LAN. In fact, the consensus among many Access developers is that the actual upper limit is more like 20 users in practice. This number can vary substantially depending on what your users are doing with the database, the size of the database, how you program their access (for example, fire-hose cursors are faster than keyset cursors), and the clock speed of your processor.

Regarding web work, I am not sure if you are talking about intranet or Internet connections. If you plan an intranet deployment, Data Access Pages (DAP) are a very attractive developing framework. It is graphical and fast to develop with for simple applications. If you plan an Internet deployment, then I recommend Active Server Pages as a developing framework. This is a more flexible development environment than the DAP environment, but you are likely to spend more time developing code.

Regarding the number of users for web work, you have your choice of using the Jet or MSDE database managers (unless, of course, you rather move up to SQL Server, which you can also manage with Access). Jet is the standard file/server database for Access. MSDE is the free version of SQL Server that ships with Access as part of Office. Microsoft programmed MSDE so that performance starts to degrade after around 5 concurrent users, but I have heard folks report satisfactory performance with as many as 40 users. Again, I think it depends on what users do with the database, how you program their access, and the power of the computers. For example, MSDE supports up to 2 concurrent processors. Jet supports just one processor, but it will run faster on a processor with a higher clock speed.

You can develop web applications for either database manager with Access and DAPs or ASPs. I also recommend using a Microsoft web server, such as IIS or Personal Web Manager. The upper limit of the number of users your solution can serve will depend on all the choices you make. Remember, however, that web connections are stateless. This means that your web clients can put a lighter load on a database than your LAN clients. Therefore, your upper limit for the number of users is higher with a web solution than a LAN solution. In fact, you could achieve a dramatically higher number of users with a web-based solution.

My sql statement is like this:

strSQL = "CREATE TABLE Janet ([ID] LONG PRIMARY KEY, [NAME]

VARCHAR(50));"

objRS.Open strSQL, objConn

When I try to insert data with this code:

strSQL = "INSERT INTO Janet([NAME]) VALUES('Smith');"

objRS.Open strSQL, objConn

I get a message that says:

primary key [ID] can't contain null value.

I thought primary key field was autonumbered automatically each time I

inserted a new record.  Why does it say that I can't have a null value for [ID]? 

My book, Professional SQL Server Development with Access 2000, includes a table summarizing comparable data type names from Access and SQL Server. It also includes how to use the IDENTITY property in different context, including how to turn it off so you can sometimes write a value into a column with the IDENTITY property. I mention the latter capability of the IDENTITY property to point out that it is not exactly the same as an AutoNumber field.

You can additionally use ADO to perform your task. Here the trick is to point a recordset object at the table. Then, enumerate the Fields collection of the recordset and print name property of each field. This will name each column in the table to which the recordset points.  Look at the book excerpt from Programming Microsoft Access 2000 for more specific help on how to accomplish this task.  Although the samples pertain to a Jet database, ADO is universal at the level of recordsets and fields.

Chapter 4 in my book, Professional SQL Server Development with Access 2000,
drills down on how to use database diagrams for SQL Server databases from
Access 2000. Among the topics it addresses are:

* adding and dropping existing tables

* creating new tables

* updating existing tables

* designating or deleting constraints for tables

* assigning or removing indexes from a table

Alter Procedure [Sales by Year]

@Beginning_Date datetime,

@Ending_Date datetime

AS

SELECT Orders.ShippedDate, Orders.OrderID, "Order Subtotals".Subtotal, DATENAME(yy,ShippedDate) AS Year

FROM Orders

INNER JOIN "Order Subtotals" ON Orders.OrderID = "Order Subtotals".OrderID

WHERE Orders.ShippedDate Is Not Null And Orders.ShippedDate Between @Beginning_Date And @Ending_Date

SELECT *

FROM dtproperties

Another site visitor reported success with your problem by running ScanDisk.  Select automatically fix errors before starting the program.