Share via

Changing Combobox source table from Access to Sql Server makes Access 2010 form uneditable.

Anonymous
2022-11-04T14:18:43+00:00

I have a field on a form in Access 2010, with a dropdown box that references a 2nd table. The dropdown box has 2 columns, one is the stored value, one is the display value.

When the 2nd table was in Access, there was no problem. When we changed the source of the 2nd table to Sql Server v.15, the form became uneditable.

The form becomes editable again when I change the ColumnWidth value of the stored value column to non-zero, i.e. make it visible.

However, the end user needs to see the display value, 2nd column, for its descriptive ability, rather than the stored value.

I'm hoping this is making sense. Anybody have any input?

Microsoft 365 and Office | Access | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

12 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. George Hepworth 22,855 Reputation points Volunteer Moderator
    2022-11-04T15:22:12+00:00

    Ah, that makes more sense.

    How about your privileges on the SQL Server table itself? You may be an "admin" on the Access side, but if your SQL Server login doesn't have the proper permissions, you won't be able to update that table. Can you edit records in it directly in the linked table's datasheet view in Access?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-11-04T14:58:15+00:00

    ALSO, someone else is able to edit the form, but we can't figure out what rights she has over what I have. I've been designated an admin.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-11-04T14:53:22+00:00

    Access seems to recognize the primary key on the attached SQL Server table. There is a key icon next to that field in the table properties window.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-11-04T14:43:48+00:00

    Under Server Properties, it says:

    Operating System: Windows Server 2019 Standart (10.0)

    Regarding primary key on the lookup table, values are not being changed there, if that makes a difference. There IS a primary key in SQL Server on the lookup table, however, the primary key field defined on the SQL Server table is not being used in the lookup functionality. If any of this makes any difference.

    Thanks for responding.

    Was this answer helpful?

    0 comments
  5. George Hepworth 22,855 Reputation points Volunteer Moderator
    2022-11-04T14:28:37+00:00

    It's not uncommon, when migrating data to SQL Server from Access and then linking the accdb to the SQL Server table to forget to designate a Primary Key on the Linked table if Access doesn't recognize it. And that makes the table uneditable. That is one possibility. There are others, but let's start with what is possibly one of the more common problems.

    SQL Server v. 15? Does that refer to SQL Server 2019?

    Was this answer helpful?

    0 comments