title: MSAccess- Changes to linked table (View) not saved
body: <p>I have an MS-Access front end to a MSSQL server back end. The existing, functional updates that the tool makes are applied through a MSSQL view which is inserted to MS-Access as a linked table. There is a primary key defined for this linked 'table' (view).</p>
  
  <p>The user sees a subset of records that match previously selected criteria, and uses comboboxes (unbound) to select the value of several fields that are then applied to all matching records using <code>DoCmd.RunSQL</code> with <code>Me.Filter</code> on the "After Update" Event.</p>
  
  <p>Users have requested an additional piece of functionality.</p>
  
  <p>I have:</p>
  
  <ol>
  <li>Added the new column required to the underlying table referenced in the view</li>
  <li>Added the column to be output in the view </li>
  <li>Refreshed the linked table in MS-Access</li>
  <li>Added the new field to the form that will be updating it, and modified the <code>DoCmd.RunSQL</code> statement to enact the <code>UPDATE</code></li>
  </ol>
  
  <p>When updating the new field via the form, I get the standard message <code>"You are about to change x rows"</code> where x is the appropriate number. Pressing OK gives no errors, but the table is not updated.</p>
  
  <p>To debug, I attempted to change the record in the linked table view directly. Again no errors were thrown, and the row seems to be updated, but this is not reflected in SSMS, and reloading the table in MS-Access the change is no longer present. I can change the values of columns other than the new one.</p>
  
  <p>I also tested adding the underlying table as a linked table and I can edit the rows in MS-Access in this table.</p>
  
  <p>(Update)<br>
  At @ErikvonAsmuth suggestion below I tried using Recordsets on the bound form instead of the <code>DoCmd.RunSQL</code>. Again could access the record and an update gave no error on <code>rst.Update</code>, but the change is not reflected in the database for the new field. I can change a previously existing field using this method as above.
  Seems my problem is independent of the update method.<br>
  (/Update)</p>
  
  <p>I would appreciate any ideas for next steps to check.</p>