Most likely it's pilot error, but I can't find what I'm doing wrong.
I have a web application with a SQLServer back end. I've created a Grid component that is updateable via a Detail form. On the Properties page of the Detail section I have checked "Check for write conflicts". On a field (call it Address) I have checked "Updateable" and "Check for write conflicts". I publish to my server, open up two browsers and do an edit that SHOULD result in a write conflict, but no error is shown.
To narrow things down I went back to the Development environment and clicked the "Show update commands" on the properties page of the Detail section, just for debugging. I open a Working Preview, click on the row hyperlink, update the "Address" field and save. The SQL Statement that is generated does NOT include a clause checking for the original value of the field (thus it's no surprise that no error is generated in the published app).
Does conflict checking only work when you're updating records direct from a grid? If not, has anyone run into this before and/or can suggest what it is I might be doing in error?
Thanks.
Edit: It SEEMS that what is causing the problem is the SQL Server column definition. In particular, when a column is defined as nvarchar(max), Alpha seems to automatically turn off the ability to do conflict checking (i.e. check for new value doesn't equal old value). Has this happened to anyone else?
I have a web application with a SQLServer back end. I've created a Grid component that is updateable via a Detail form. On the Properties page of the Detail section I have checked "Check for write conflicts". On a field (call it Address) I have checked "Updateable" and "Check for write conflicts". I publish to my server, open up two browsers and do an edit that SHOULD result in a write conflict, but no error is shown.
To narrow things down I went back to the Development environment and clicked the "Show update commands" on the properties page of the Detail section, just for debugging. I open a Working Preview, click on the row hyperlink, update the "Address" field and save. The SQL Statement that is generated does NOT include a clause checking for the original value of the field (thus it's no surprise that no error is generated in the published app).
Does conflict checking only work when you're updating records direct from a grid? If not, has anyone run into this before and/or can suggest what it is I might be doing in error?
Thanks.
Edit: It SEEMS that what is causing the problem is the SQL Server column definition. In particular, when a column is defined as nvarchar(max), Alpha seems to automatically turn off the ability to do conflict checking (i.e. check for new value doesn't equal old value). Has this happened to anyone else?