Optimistic concurrency misses varchar fields?

Question

I am trying to create a very simple typed dataset using the designer in VS2005 to connect to my Article table on an SQL Server 2005 Express database, nothing out of the ordinary. I want to use optimistic concurrency because there will be many user working on that table.

But it seems that when I drag my table on the dataset designer's surface from the server explorer window, it does not create the update and delete queries correctly for concurrency issues detection. There are filters missing on the varchar(MAX) fields so another user may modify the article's content and I won't even know it when I overwrite their change.

This is shown on the screenshots I attached. You can see there is no filter on any of the VARCHAR(MAX) columns.

Is this caused by the full-text search option being disabled? It seems to solve the problem if I modify the DELETE and UPDATE queries manually, but I'm looking to know why it generates them that way and how I can make it work correctly instead of modifying all my queries manually (that's hours of boring work). Performance isn't an excuse to cut the corners that rough...

Article table structure.JPG
Article delete query.JPG