No problem

Well, I can already tell you that you will end up on top of things and be successful with your application.  You have an open mind and are willing to learn and adopt new things and techniques.  This is how you get on the top of the pile!

We live in a continuously changing business and we too are always learning better and more efficient ways to do things...so we refactor our code very often as well.

Thanks for the help Trent & Edhy Rijo. Much appreciated.

Trent,

Thanks for the info.  I am sure I'll have a lot fun in the training with all the material to cover.  So far with the help of SF I am doing pretty good with this project and I am sure many things will have to be re-written after the training , but for now, just trying to keep things put and getting ready for the training.

Edhy Rijo

It will be auto-managed just as the SQL Server and others do.

Regardless of the database, row versioning is always the best method as the query is far less complicated than when using all fields.  This is actually a section that we cover during training and show the massive differences between using row versioning and any other type of checking.

Hi Trent,

One question, will the Version field be incremented automatically by SF or do we have to update this field in every change of the record to trigger the concurrency rule?

Also what would be the reccomended concurrency rule for MS-SQL2005?

Edhy Rijo

The only way that the concurrency will work with Access is by using a row version field.  The Optimistic all fields and timestamp options will not work with Access.  If you create a row version field and then set the CRUD settings on the BO, it will work.  I updated and posted the sample that you had started.  When you create the version field, be sure to have all records update with a 0 for teh default value or it will not work.  The reason is when you add the new version field it will basically be empty...so it will get overlooked.

Ok, I am able to duplicate your results.  Have you tried with OptimisticTimeStamp or OptimisticRowVersion?

My guess is that somehow Access is either not sending the event or SF is not catching it.

Edhy Rijo

The steps to reproduce what SHOULD cause an concurrency exception is to start the project, and after the form loads and displays the values, open the database with Access and change the values of the table and save the changes. Then click the save button on the app.



When I do the same steps using SQLExpress, I get the concurrency exception which is what I need to happen.



Thanks for checking it out.

Hi Crones,

I willing to test your sample project, please post steps to do the same test you are doing.

Edhy Rijo