Just started working with Access to SQL Server 2005 Migration. I have 3 tables and out of the 3 tables, I can only add/edit/update 1, when I finished the Migration.
What should I look for, where would most likely the problem exist

first up:

Does each table have a primary key defined (check to see that in the SQL Server tables it has a field defined as a primary key).

Bob, when you say "first up", I know I am going in for a good lesson.
Yes, each table DOES have a primary key

BTW thanks for quick reply

Then, how have you relinked the tables (what steps)?

Bob, we have not yet tried to re-link them in the second try. The first try, all but 1 of the 3 tables works correctly. I have not yet, watch my mentor how he is going to re-link on the second try.
Like I said I am on a real learning curve here. Now he did mention that he is going to link the queries as well, I guess you do that so you can view them. I just thought maybe we should be on the lookout for unseen problems.

I will say this SQL, is something else. I will keep you posted on how this is progressing.

hi,i also met the same problem.so how to solve it?
i already import all the table in sql express 2008 but when i try to do change with the old data in the access front system it is not any change or update in the table in sql.

Still very new to SQL, when we migrated the second time, I notice he changed some null fields in the SQL to accept. I think that is where the problem came from. Now we are trying to migrate when adding a new record, that is our next issue. I think when this is solved, this should do it. I have notice when migrating there is a lot of small details that you have to look at before you start.

Ok, still having problems. At the second time we got message "skipping tables". I double check and made sure that every table has a Primary Key, now I am 100% sure. Now for some reason we cannot get all the data in one of main tables. Out of 7,000 records we only get 75. At one time we got all, but could not update any of the records.

Any clue what else we can look at it. We tried SQL 2005 and 2008, we even used the up sizing tool that is located in Access. Still no luck. I think its something we are doing on our side with the SQL, but I can't put my finger on it. I am watching and trying to learn at the same time, so I can't pinn point anything.

Any help would be great.

The person who knows SQL mention that I might have to maunally write each colum.

Have you seen this (http://www.microsoft.com/sqlserver/2005/en/us/migration-access.aspx) yet?

Bob, you hit it right one the head at the first reply, Primary Key, Primary Key, Primary Key. What I thought the Auto Number makes it the Primary Key, but when I look again YOU MUST set it as a primary key (ICON)..duh.

Also found out that if you have a date field and the field has two seperate words like "Dtd Sign", the SQL does not like that, so then its puts in brackets [Dtd Sign]. Everyone told me that will come back and haunt me some day. Well it did.

So here is the bottom line, we have the big hurtle done, all tables and etc came over with no errors. YEA.

So now we are in the learning curve of setting the security. Don't know how that is going to work now, since we have it on SQL server. I did have it located on a network drive. So this should be interesting.

Comes down to alot of testing. I just like to thank everyone for helping me out on this.

This forum has saved my butt so many times. Hats off to all of you.

Glad we could assist. Good luck with the rest of your project. :)