Just when I though I was done.....I have been instructed to Web Enable the database I am using to a sharepoint server.
Looked easy enough. I ordered some server space and ran the compatability check. Had a few issues which are easy to resolve, but one I don't think I should have to and was wondering if someone knew why Access would make this an issue.
I have a table with Material codes which is unique for each material being used in a product. The material code is unique for each item and can not be duplicated so I set the material code as a primary key. Because the material code can contain letters as well as numbers I made it a text field.(Example: F60569, 703556, L32R69)
My problem is when I go to publish the database to the web it kicks it back saying that the primary key field should be a number with field size long to be compatible.
I know I can just add an auto number to the table, but why would it not accept it the way it was. Creating an autonumber key makes no sense when the code itself can be a Primary key.... at least to me it doesn't make sense.
Looked easy enough. I ordered some server space and ran the compatability check. Had a few issues which are easy to resolve, but one I don't think I should have to and was wondering if someone knew why Access would make this an issue.
I have a table with Material codes which is unique for each material being used in a product. The material code is unique for each item and can not be duplicated so I set the material code as a primary key. Because the material code can contain letters as well as numbers I made it a text field.(Example: F60569, 703556, L32R69)
My problem is when I go to publish the database to the web it kicks it back saying that the primary key field should be a number with field size long to be compatible.
I know I can just add an auto number to the table, but why would it not accept it the way it was. Creating an autonumber key makes no sense when the code itself can be a Primary key.... at least to me it doesn't make sense.
Last edited: