Microsoft KB Archive/229681

= ACC2000: Cannot Use Upsized Append and Make-Table Queries in an Access Project =

Article ID: 229681

Article Last Modified on 8/9/2004

-

APPLIES TO


 * Microsoft Access 2000 Standard Edition

-



This article was previously published under Q229681



Advanced: Requires expert coding, interoperability, and multiuser skills.

This article applies only to a Microsoft Access project (.adp).

For a Microsoft Access 2002 version of this article, see 294923.



SYMPTOMS
When you try to run upsized make-table or append queries in a Microsoft Access project, you may receive the following error message:

Cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option.

-or-

Cannot insert explicit value for identity column in table table name when IDENTITY_INSERT is set to OFF.

You may also encounter the first error message when running an upsized update query.



CAUSE
When you create a new Microsoft Data Engine (MSDE) or SQL Server database, the select into/bulkcopy and IDENTITY_INSERT options are set to OFF.

Upsized Make-Table Queries
When you upsize a database that contains make-table queries, the queries migrate as stored procedures. These stored procedures use the SELECT INTO statement to create a new table and then add records to it. You must set the select into/bulkcopy option of the database to ON in any database that contains a stored procedure that uses the SELECT INTO statement.

Upsized Update and Append Queries
If you upsize a Microsoft Access table that contains a field of the AutoNumber data type, the field will be created on MSDE or SQL Server as an IDENTITY column. Unlike the AutoNumber data type, you cannot directly edit IDENTITY columns, nor explicitly insert data into an IDENTITY column while the IDENTITY_INSERT option for that table is set to OFF. To insert or update data in an IDENTITY column, you must set the IDENTITY_INSERT option to ON.



RESOLUTION
To set the select into/bulk copy option to ON for your database, create a stored procedure that uses the sp_dboption system stored procedure to toggle the setting. The following SQL sample modifies a database named MyDatabase so you can use SELECT INTO statements:   CREATE PROCEDURE SetMyOptions AS  EXEC sp_dboption 'MyDatabase','bulkcopy','ON' You can use the SET IDENTITY_INSERT statement to set the IDENTITY_INSERT option. SET IDENTITY_INSERT always references a table, and should be placed before the UPDATE or INSERT statement that modifies or inserts data into an IDENTITY column. The following example sets IDENTITY_INSERT for the NewEmployees table.   SET IDENTITY_INSERT NewEmployees ON



MORE INFORMATION
When you try to upsize to SQL Server 2000 from Access 2000 using the Upsizing Wizard you receive an "Overflow" error message. For additional information about this issue, click the article number below to view the article in the Microsoft Knowledge Base:

272384 ACC2000: "Overflow" Error Message When You Try to Upsize to SQL Server 2000

Steps to Reproduce Behavior
 Open the sample database Northwind.mdb. Create a new query in Design view, and close the Show Table dialog box without adding any tables or queries. On the View menu, click SQL View.  Type the following SELECT statement into the SQL window. It will create a make-table query: <pre class="fixed_text">  SELECT Employees.EmployeeID, Employees.LastName, Employees.FirstName, Employees.Title, Employees.TitleOfCourtesy, Employees.BirthDate, Employees.HireDate, Employees.Address, Employees.City, Employees.Region, Employees.PostalCode, Employees.Country, Employees.HomePhone, Employees.Extension, Employees.Photo, Employees.Notes, Employees.ReportsTo INTO NewEmployees FROM Employees; </li> Save the query as qryMakeTable, and then close it.</li> Create a second query in Design view, and close the Show Table dialog box without adding any tables or queries.</li> On the View menu, click SQL View.</li>  Type the following INSERT INTO statement into the SQL window. It will create an append query: <pre class="fixed_text">  INSERT INTO NewEmployees (EmployeeID, LastName, FirstName, Title,         TitleOfCourtesy, BirthDate, HireDate, Address, City, Region,          PostalCode, Country, HomePhone, Extension, Photo, Notes,          ReportsTo) SELECT Employees.EmployeeID, Employees.LastName, Employees.FirstName, Employees.Title, Employees.TitleOfCourtesy, Employees.BirthDate, Employees.HireDate, Employees.Address, Employees.City, Employees.Region, Employees.PostalCode, Employees.Country, Employees.HomePhone, Employees.Extension, Employees.Photo, Employees.Notes, Employees.ReportsTo FROM Employees; </li> Save the query as qryAppend, and then close it.</li> On the Tools menu, point to Database Utilities, and then click Upsizing Wizard.</li> Complete the steps in the Upsizing Wizard, using default selections, except where noted below:

Create New Database: Yes

Which tables do you want to export to SQL Server: Export all tables

Add timestamp fields to tables: No, never

Create a new Access client/server application: Yes

</li> Once the upsizing tool has completed its work, close the upsizing report.</li> Try to run the qryMakeTable stored procedure, and note the error message.</li>  To set the select into/bulkcopy option to ON, create a stored procedure using the following SQL: <pre class="fixed_text">  CREATE PROCEDURE SetMyOptions AS  EXEC sp_dboption 'NorthwindSQL','bulkcopy','ON' </li> Save and run the stored procedure SetMyOptions.</li> Run the stored procedure qryMakeTable again. Note that this time it succeeds.</li> Try to run the qryAppend stored procedure and note the error message.</li>  To set IDENTITY INSERT to ON, add the following line of SQL to the qryAppend stored procedure directly after the keyword AS: <pre class="fixed_text">  SET IDENTITY_INSERT NewEmployees ON When complete, your stored procedure should resemble the following text: <pre class="fixed_text">  ALTER PROCEDURE qryAppend AS  SET IDENTITY_INSERT NewEmployees ON   INSERT INTO NewEmployees (EmployeeID, LastName, FirstName, Title,         TitleOfCourtesy, BirthDate, HireDate, Address, City, Region,          PostalCode, Country, HomePhone, Extension, Photo, Notes,          ReportsTo) SELECT Employees.EmployeeID, Employees.LastName, Employees.FirstName, Employees.Title, Employees.TitleOfCourtesy, Employees.BirthDate, Employees.HireDate, Employees.Address, Employees.City, Employees.Region, Employees.PostalCode, Employees.Country, Employees.HomePhone, Employees.Extension, Employees.Photo, Employees.Notes, Employees.ReportsTo FROM Employees </li> Save the modified stored procedure, and then run it. Note that it succeeds.</li></ol>

<div class="references_section">