katrina11
Technical User
- Apr 30, 2011
- 108
Hi experts!
There is an Access 2007 application with fake data and it works just perfect.
However when I am trying to import a real data table from Excel 2007, system doesn’t allow me to create a primary key and generates a warning message:
"The changes you requested to the tables were not successful because they would create duplicate values in the index, primary key or relationship. Change the data in the fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entry ad try again".
I attempted to change real data table’s names in order to “mislead” the system but it did not allow me to create Pk anyway.
After I have ignored the warning and tried to copy all properties
for this field from the fake data table structure (as well as for all others field),system still did not allow me to create a primary key.
I attempted to delete old tables first....no effect. Whatever I do there is no result. Same warning pops up.
Actually initial properties for ProviderID filed are the followings:
Required: No
Allow zero length: YES
INDEXED: Yes (No Duplicates)
Unicode Compression: YES
Actually in a process of importing I chose the same property for
ProviderID
I broke my head. There is a lot of stuff in the application (which somebody created in the past),including many forms and queries and macros. It works perfect with fake data and I cannot believe that I will have to create it from scratch
What I am doing wrong? Please, give me a hand. Thank you for any help with the issue.
Katrin
There is an Access 2007 application with fake data and it works just perfect.
However when I am trying to import a real data table from Excel 2007, system doesn’t allow me to create a primary key and generates a warning message:
"The changes you requested to the tables were not successful because they would create duplicate values in the index, primary key or relationship. Change the data in the fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entry ad try again".
I attempted to change real data table’s names in order to “mislead” the system but it did not allow me to create Pk anyway.
After I have ignored the warning and tried to copy all properties
for this field from the fake data table structure (as well as for all others field),system still did not allow me to create a primary key.
I attempted to delete old tables first....no effect. Whatever I do there is no result. Same warning pops up.
Actually initial properties for ProviderID filed are the followings:
Required: No
Allow zero length: YES
INDEXED: Yes (No Duplicates)
Unicode Compression: YES
Actually in a process of importing I chose the same property for
ProviderID
I broke my head. There is a lot of stuff in the application (which somebody created in the past),including many forms and queries and macros. It works perfect with fake data and I cannot believe that I will have to create it from scratch
What I am doing wrong? Please, give me a hand. Thank you for any help with the issue.
Katrin