On Wednesday, August 31, 2011 09:44:22 am Ed Leafe wrote: > On Aug 31, 2011, at 11:39 AM, Paul McNett wrote: > > I think your points are reasonable. Dabo should define which keys are > > available for a given backend. I agree that the "extra stuff" key > > doesn't belong in the XML or to display to the user in CxnEditor, > > however I think there should be a way to get something working in code > > if we haven't yet implemented a valid key in Dabo. > > True, but the entire connection mechanism is different: we can't use the > dConnectInfo/dConnection classes without some major changes, as we don't > have any support for connection strings. Those classes are predicated on > dbapi-style connections, and the ODBC classes will require some additional > work to be able to recognize ODBC-type backends and craft the appropriate > connection string instead of setting attributes from the keys. > > > -- Ed Leafe
I gather that the consensus is to maintain a list of keys for each of the suggested databases (mssql, dbf). I will first attempt to get the mssql working and see what is required with a simple hand coded form. Then move on to see what is required to setting up the keys. Johnf _______________________________________________ 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]
