On Mon, Jun 30, 2008 at 12:54 PM, Ed Leafe <[EMAIL PROTECTED]> wrote: > On Jun 30, 2008, at 1:23 PM, Paul McNett wrote: > >> I guess we could coerce it, no real harm done. However, I think that >> the >> CD should store it as an int instead of a unicode, but doing such >> automatic coercions would hide such problems and keep them from being >> solved. My inclination is to put in asserts for such situations >> where we >> expect certain data types, and then fix the discovered problems. > > > All attributes in XML are strings; that's just a fact of life. When > the design is created from the XML, the values are passed in the > 'attProperties' parameter, which differs from the regular 'properties' > parameter in that its values are interpreted as the underlying > property's type. In the case of Order, it should be eval'd to an int > before it is assigned to the column's Order prop.
Hmm. Every more interesting is the fact that my main cdxml form is working just fine, but this error and now other errors with various other properties pop up when I call a dialog designed by the CD. Nate L. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
