> > The problem is that the dirty flag is not set when dot notation is > used against an object field. In your scenario the following will work > … .... field modified = field modified --right?!?! > OB SET ([Table1]Object;”value”;b_value) //this will set the record dirty. > > And, yes, I too was told that the engineers were leaning to declaring > this as standard behavior. Why? I have not a clue. see above ------------ Hell is other people Jean-Paul Sartre ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
- [Warning] Settings properties values on obje... Alberto Bachler via 4D_Tech
- Re: [Warning] Settings properties value... Chip Scheide via 4D_Tech
- Re: [Warning] Settings properties v... Wayne Stewart via 4D_Tech
- Re: [Warning] Settings properties v... Arnaud de Montard via 4D_Tech
- Re: [Warning] Settings properties value... John Baughman via 4D_Tech
- Re: [Warning] Settings properties v... David Adams via 4D_Tech
- Re: [Warning] Settings properties v... Chip Scheide via 4D_Tech
- Re: [Warning] Settings properti... John Baughman via 4D_Tech
- Re: [Warning] Settings prop... Chip Scheide via 4D_Tech
- Re: [Warning] Settings prop... David Adams via 4D_Tech
- Re: [Warning] Settings... Charles Miller via 4D_Tech
- Re: [Warning] Sett... Lee Hinde via 4D_Tech
- Re: [Warning] Settings properties v... Tom Swenson via 4D_Tech
- Re: [Warning] Settings properti... Tom Swenson via 4D_Tech
- Re: [Warning] Settings properties value... David Adams via 4D_Tech
- Re: [Warning] Settings properties value... Ben Kershaw via 4D_Tech
- Re: [Warning] Settings properties v... Keisuke Miyako via 4D_Tech