Paul McNett wrote: > Carl Karsten wrote: >> Paul McNett wrote: >>> Ed Leafe wrote: >>>> On Feb 12, 2007, at 11:38 PM, daryl warder wrote: >>>> >>>>> I was wondering if this is a bug or is the word 'Name' a reserved >>>>> word in Dabo ? >>>> Well, we haven't formally defined 'reserved words' in Dabo, but yes, >>>> 'Name' has a specific meaning in Dabo. Every UI object has a Name >>>> property that must be unique among its siblings. Looking at the code >>>> in question, the presence of 'Name' is definitely the problem. >>>> >>>> I suppose I should add a wiki page containing a list of reserved >>>> words for Dabo. Thanks for the feedback! >>> IMO, we should fix the problem instead. The reserved words are >>> effectively every single property or method in the bizobj. Our code >>> should first try to get the value from the record, and only if the field >>> isn't found should we try to resolve a property or method reference. >>> >>> I use 'name' as a field name all the time, but never got hung up on this >>> because of case-sensitivity. >>> >> I am curious as to why it even collides. >> >> I would expect to see an attribute called .FieldName, and in this case its >> value >> is 'name' or 'Name'. >> >> Why do we end up with .foo being created if the fieldname is 'foo' ? > > I think you misunderstand the problem. The db has a fieldname named > "Name". The textbox is bound to a DataSource and DataField of > "customers" and "Name". "customers" resolves to bizCustomers, but "Name" > resolves to property Customers.Name instead of field Customers.Record.Name. >
is """ "Name" resolves to property Customers.Name """ a bug? Carl K _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
