Write conflict on active link SQL table

[JohnD88]

I'm just starting the process of migrating a Filemaker solution to A5 and have run into a wall. I have an active link table connected to a sql express 2005 source and when I try to change a record in it on a desktop form, I almost always get a Write conflict warning saying the record has been edited by another user. I say "almost" because once or twice, and only on certain records, it will save the changes. Stranger still, on a web grid connected to the same table, records update on it no problem. FYI, there is no one else connected to the data. Any suggestions?

[Selwyn Rabins]

Re: Write conflict on active link SQL table

I'm just starting the process of migrating a Filemaker solution to A5 and have run into a wall. I have an active link table connected to a sql express 2005 source and when I try to change a record in it on a desktop form, I almost always get a Write conflict warning saying the record has been edited by another user. I say "almost" because once or twice, and only on certain records, it will save the changes. Stranger still, on a web grid connected to the same table, records update on it no problem. FYI, there is no one else connected to the data. Any suggestions?

i am not seeing this problem in my tests in which i have a copy of northwind in sql server.

we can give you a quick answer to your question if you send us the table structure of your sql server table.

you need to go into the sql server express management studio and right click on the table. you should see a command to copy the sql create table statement. that's what we need.

once we have the create table statement we can recreate an identical table and test the update.

in the mean time, i suspect that you can work around the problem by editing the active link definition and changing the 'update sql' statement from auto generated to custom.

then when you create your custom update statement, just select the primary key field, not all fields, for the WHERE clause in your Update statement.

thanks

[JohnD88]

Re: Write conflict on active link SQL table

Mr. Rabins,

Thank you for your quick answer. I think I finally found the sequel create statement from SSMSE which is attached. I did change the UPDATE statement on the active link to Primary Key only and it worked. Now I can edit the records. I received a warning when I did this. Does this interfere with the Optimistic record locking? Thanks again for your quick reply.

[Selwyn Rabins]

Re: Write conflict on active link SQL table

Mr. Rabins,

Thank you for your quick answer. I think I finally found the sequel create statement from SSMSE which is attached. I did change the UPDATE statement on the active link to Primary Key only and it worked. Now I can edit the records. I received a warning when I did this. Does this interfere with the Optimistic record locking? Thanks again for your quick reply.

thanks for the sql create statement.

i was able to create a table and populate it with dummy data and then create an active-link table.

i did not have any trouble at all doing updates.

i did not need to change my update where clause to be 'primary key only'. it is possible that this is because I am using a pre-release of the next update which will come out next week some time.

in any event, when you set the update where clause to be 'primary key only' a5 was just warning you that it would NOT be able to trap 'optimistic lock errors'. it is just a warning that is displayed to make sure you know what the consequences are of modifying the system generated update where clause.