Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Refreshing a linked table (housed on MS SQL Server) now breaks

Refreshing a linked table (housed on MS SQL Server) now breaks

Refreshing a linked table (housed on MS SQL Server) now breaks

We had a former developer who built most of the forms in our MS Access database. When we first built the database in Access office 365 we did refreshing of tables from our dev version before publishing to production. All was great back then, before the revamping of the managing of linked tables. Since the rework on linked table manager we can no longer just refresh a table. It now asks what we want to use for Unique Record Identifiers. I do not know what the former developer used for those, but from my research I've been doing fine with the cancel at that screen. We manage the record identifiers at the SQL server side. WELLLLLLLL... now I have ONE table that works great from an archive version, but for only one table I do a refresh & the cancel at Unique question give me an error within a form. The error is either something got corrupted or there was a Unique mapping. How can I find out what the Unique identifier options were selected (if they were used) or is it a corrupt (something)??

The error I now get is Run-time error '2105': You can't go to the specified record.

I am at a loss how do deal with this.


RE: Refreshing a linked table (housed on MS SQL Server) now breaks

*thinking* wonder why this thread is not getting any attention.

RE: Refreshing a linked table (housed on MS SQL Server) now breaks

What access does behind the scenes is create an index representing the unique fields when you do that.
I would look into inspecting the index on the linked table. I've not had to do this myself.
I think many of us don't visit these threads often now... I have my own problem in other topics about corruption and hoping someone else has hit the pain...

RE: Refreshing a linked table (housed on MS SQL Server) now breaks

When you link to the SQL Server tables I assume you are being asked to identify the unique columns/fields.
Are there primary keys or unique indexes on the SQL Server tables?
Every table should have a primary key. If not, I would add one on the SQL server table.

You can also use a DDL query on the Access side to create a unique index. Of course the chosen field(s) must be unique.

Hook'D on Access
MS Access MVP 2001-2016

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close