run project in network

[Dalek Dave]

Good advice.

------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave CCC Link[^] Trolls[^]

[Dave Kreskowiak]

Yeah, and the flag would never get reset. What he wants just isn't really feasible to do and still have fault tolerance. One possible cause of a "failure" would be if Windows shutdown while the record was 'checked out' for edit.

A guide to posting questions on CodeProject[^]
Dave Kreskowiak

[dan sh]

As Richard suggested, this question suits better in the Database forum. You can make use of with(rowlock) in your update statement. This will help you avoiding multiple edits on the same row. You can also make use of rowversion to do this. I don't know much about rowversion way but someone in database forum should be able help with this.

"Your code will never work, Luc's always will.", Richard MacCutchan[^]

[Luc Pattyn]

and once you're in the Database forum, have a look at this thread[^]; I think it relates to what you want. :)

Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.

[Luc Pattyn]

Optimism is a great virtue, but not for a software developer... :(

Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.

[slam Iqbal]

Hi, look at my Code. In my code DB_Command.Transaction = DB_Connection.BeginTransaction(System.Data.IsolationLevel.Serializable); defines transaction level. It locks(for update/insert) the database until the command is committed. Please never use flags.

    public void Execute(string querystring)
        {
            DB\_Command = new OleDbCommand(querystring, DB\_Connection);
            //DB\_Command.Transaction = DB\_Connection.BeginTransaction(System.Data.IsolationLevel.ReadCommitted);
            DB\_Command.Transaction = DB\_Connection.BeginTransaction(System.Data.IsolationLevel.Serializable);
            DB\_Command.CommandType = System.Data.CommandType.Text;
            int afr=DB\_Command.ExecuteNonQuery();
            DB\_Command.Transaction.Commit();
        }

[jojoba2011]

Thanks for reply. But no use of these solutions.

[Lost User]

The best solution is to set a flag (with date/time) and check the flag before starting an edit session. If there is a possibility of a client not being able to reset the flag (ex: restart) before completing the edit, run a job in the background to check for flags that are open for the last x mins and reset those flags.

[Ganesh Kumar Kaki]

Hi everyone, I'm also facing same kind of problem. Any help would be appreciate.

[Dave Kreskowiak]

Then read the entire thread and figure out that what you want isn't really possible. You simply have to do research on "database concurrency" and pick the best option that fits your requirements.

A guide to posting questions on CodeProject[^]
Dave Kreskowiak