Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A few comments:</p> <ul> <li><p>is there any particular reason you save the form's data (set <code>Dirty=false</code>) before changing the other field's value (which will make the form dirty again)?<br> I would first change the other field's data <em>then</em> save the form's data, otherwise the form is <em>always dirty</em>.</p></li> <li><p>changing control's values from code does not call their events, so changing <code>chkSupRequirePrice</code>'s value from <code>chkSupAllowBlankPrice_AfterUpdate()</code> will not call <code>chkSupRequirePrice_AfterUpdate()</code>.</p></li> <li><p>Instead of putting specific code into each event, it's better to regroup everything into the same, say, <code>Update()</code> sub called from each event handler.<br> It will make it easier to manage you code and its side effects because it's the same piece of code that's called all the time.</p></li> <li><p>having said that, your code <em>should work</em>, so I'm guessing the issue comes from somewhere else in your code.<br> Write conflicts happen if the same record is already opened for editing elsewhere.<br> You can play around with the type of locking and see if it changes anything.</p></li> <li><p>to see if the issue is really related to your SQL Server setup, try to unlink the table and instead copy it into your local Access database to see if you're still getting this issue when dealing with a local Access table.</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POWrite Conflicts - even with me.dirty
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRenaud Bompuis
    1. USRenaud Bompuis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI tried editing the straight table on which the query is based, on which the form is based which started this whole thing. It won't let me edit values for already entered records, despite edits being allowed on the form. I get the same Write Conflict dialog, except if I log into the server and enter the values directly from within the Server Management Studio console.
      singulars
      1. PO
      1. USComrad_Durandal
    2. CODo you mean you can't edit the data once the underlying original table is bound to the form? What error are you getting? Did you try to get the table and its data from SQL Server to reside in your local Access database? Are you still getting these errors? It's going to be hard to get an answer to your problem without having a look at the whole thing. Maybe the query is too complex and it's become read-only. Unfortunately, the problem doesn't seem to be located in what you provided here, so it's hard to guess.
      singulars
      1. PO
      1. USRenaud Bompuis
    3. COBasically, I tried to enter data into the datasheet view of the query on which the original form was based - and I still got a write conflict. I went to the linked table within the Access application from which the query was generated, and it too gave me a Write conflict when I tried to alter existing values. The only way the data was accepted was if I went to the SQL Server's management console directly, executed a 'Edit Top 100 records' and enter the data there. Then it would update.
      singulars
      1. PO
      1. USComrad_Durandal
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload