> > The key is to make sure that the record upon which you want to act > (delete/update) currently > selected; either through the UI (e.g., selecting the row in a grid), or > programmatically (e.g., > form.moveToRowNumber()). Then when delete() is called, that will be the > record to delete. > > For updates, the same general thing applies: selecting the desired > row will cause that row's > data to be displayed in any bound UI objects, and changing those values will > affect just that row. > However, saving those changes is buffered, so when you modify the values, > they are not written > immediately to the backend store; they are only changed in the local dataset. > When you call > form.save(), Dabo will find all your changes and save them, even if you have > moved to a different > row in the bizobj. This behavior is the default; you can change it by setting > the form's SaveAllRows > property to False. If you do that, only changes in the current row of the > PrimaryBizobj (and related > child rows) will be saved. > > -- Ed Leafe > > To make my question more clear, pl. consider the vfp cursor adapter. In the cursors added to data-environment, records are either updated or marked for deletion or appended. At the end, with just a single call, it takes care of the CRUD functions automatically.
Whether such behaviour like vfp CA is possible here? -- Vineet --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: Dabo-users@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/CAP5=7or-=wRPL11Pn5sNx3gUbCXCoJgpN+6CKmEn_Mr1f4i=j...@mail.gmail.com
