[quote="GaneshS":2v8u3z3a]Yes there is no need to double check the data . But I am worried about if i am compare the mode=edit and update my other dependent table but at very rare case if our main edit query failed due to some access violation of DB constraint . That create the problem .[/quote:2v8u3z3a]You shouldn't encounter problems like that. It's rather safe to assume it won't happen.
[quote="GaneshS":2v8u3z3a]I want to ask another question
What is the right way to create custom module , I have following three choice :-
1. Using RecordBrowser as you created.
2. Using GenericBrowser with write our custom function for add,edit,delete,save,view etc.
3. Simple module :- As you created FORUM module. Write all custom function
Thanks.[/quote:2v8u3z3a]
All three methods are perfectly valid. RecordBrowser will help you take care of some minor annoyances like dirty read, viewing history, edit history, select fields, etc. But on the other hand, few things can be little bit more efficient (RecordBrowser is generic module) if you write your module based on simpler bricks like Generic Browser, QuickForm and such.
And in fact options 2 and 3 don't differ much - it's just matter of using other modules or not, which isn't necessary, but quite handy. I doubt hard-coding html table with sorting would be worthy concept if you can simply use Generic Browser. 🙂
Cheers,
Arek