Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.
View products that this article applies to.
| � | If you do not have a unique index on the field that contains Null values, the table is upsized as well as the data. |
| � | If the field has a unique index but ignores Null values, the number of records deleted will be the count of the null records, but none of the data is upsized. |
| 1. | Open the original Access database (.mdb). |
| 2. | Open the problem table in Design view. |
| 3. | On the View menu, click Indexes. |
| 4. | Delete the index that is on the Replication ID field that contains the Null values. |
| 5. | Upsize the database. The table should be upsized with all the data. |
| 6. | Open the target SQL Server database, either in SQL Server Enterprise Manager or in an Access project. |
| 7. | Open the table in Design view. |
| 8. | Right-click anywhere in the table design area, and then click Properties. |
| 9. | In the Properties dialog box, click Indexes/Keys. |
| 10. | Click New. On the first blank row under Column Name, select the column on which you want an index. In the Index Name box, accept the default index name or type a different name. |
| 11. | Change any of the other default settings for the index if you need to. |
| 12. | Close the Properties dialog box. |
| 13. | Save and close the table. |
| 1. | Create a new Access database, and name it UpsizeTest.mdb. |
| 2. |
In the new database, create a table with the following specifications, and then save it as tblTest:Table Fields: tblTest ---------------------------- Field Name: Col1 Data Type: Number Field Size: Replication ID Indexed: Yes (No Duplicates) Field Name: Col2 Data Type: Number Field Size: Replication ID Indexed: Yes (No Duplicates) Field Name: Col3 Date Type: Text Field Size: 20 Indexed: Yes (Duplicates OK) Table Properties: tblTest ------------------------- PrimaryKey: Col1 Index1: Col2 |
| 3. | Save the table, and then view it in Datasheet view. |
| 4. |
In the Col1 field, type the following Replication IDs (be sure to include the braces {}):
{17DC72A1-F0E1-4F59-AF0D-F3D413269A32}
{302AD122-01E0-49EF-B2A6-D28681E34B97}
{30ABD2AB-7494-4CCB-86CF-8FD524E51EF5}
{36D901D5-4EA6-4D4B-A670-CE87E98BC1E0}
{9CFAC60E-FC56-4F98-AD0C-5B63E3E0D41F}
{ED0950B4-D8F7-4B90-8936-AE29CA011688}
{FD82B066-4758-477B-A112-FBB22AC2585E}
|
| 5. |
In the Col2 field, type the following Replication IDs. Leave the field blank for the last three records:
{17DC72A1-F0E1-4F59-AF0D-F3D413269A32}
{302AD122-01E0-49EF-B2A6-D28681E34B97}
{36D901D5-4EA6-4D4B-A670-CE87E98BC1E0}
{9CFAC60E-FC56-4F98-AD0C-5B63E3E0D41F}
|
| 6. |
In the Col3 field, type the following names:Sam Nick John Terry Mike Joe Don |
| 7. | Save and close the table. |
| 8. | On the Tools menu, point to Database Utilities, and then click Upsizing Wizard. |
| 9. | Select to use an existing SQL Server database, and then click Next. |
| 10. | Select the appropriate DSN to connect to your SQL Server, and then click OK. |
| 11. | On the page that asks you which tables to upsize, double-click tblTest so that it appears on the right. |
| 12. | Click Next twice. |
| 13. | On the page that asks you which application changes you want to make, click Link SQL Server tables to existing application. |
| 14. | Click Finish. Note that you receive the error message mentioned in the "Symptoms" section of this article. |
| 15. | Click Yes to proceed with upsizing. |
| 16. | Close the resulting Upsizing Report. In the list of tables, you see that the original table is now called tblTest_local, and a new attached table to the upsized table has the original name with a globe icon, as expected. |
| 17. | Open the attached table, tblTest, and note that no data has been upsized. |
Keywords: KB253757, kbnofix, kbbug