Kirk: What you're describing doesn't sound like a "feature", that's for sure.
Obvious question - are you sure that the object itself is closed? Also, any chance the structure is in read only? Dollars to doughnuts you've covered those bases but just in case⦠Another option would be to try this in a newer version. I haven't seen a mention of an issue like this in a "fixed bugs" document but, again, it might be worth trying to get a better understanding of what is(n't) happening. -- Douglas von Roeder 949-336-2902 On Sat, Mar 11, 2017 at 5:35 PM, Kirk Brooks via 4D_Tech < [email protected]> wrote: > This is the first time I'm attempting to use METHOD SET CODE on form > objects in a v13.6 db. > > There's nothing tricky about what I'm doing: export methods from one > database and import into another. Project methods all work flawlessly but > object methods just don't. > > I verified the method paths are the same by having the import method call > METHOD GET CODE first (in the debugger I see it is opening the object > method and getting the code) them call METHOD SET CODE to write the > imported code. For testing I then called METHOD OPEN PATH - to see that > nothing is actually changed. > > Is this just a v13 bug? I'm really stumped here. > > -- > Kirk Brooks > San Francisco, CA > ======================= > ********************************************************************** > 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:[email protected] > ********************************************************************** ********************************************************************** 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:[email protected] **********************************************************************

