ODBC Implementation Question...
> Also what are the other main selling points beyond ODBC database access
> at this stage...?
> Command won't talk directly to mySQL, but you'll be able to access it
> through ODBC. Native d-base implementations are slated for early Q1 (also
> including Oracle, Sybase, etc.).
Quick question - are you attempting to stick with the somewhat standard
ODBC API used in everything from PHP to VC++ to LotusScript? By this I
mean the somewhat usual combo of:
Connection -
Usually you set the DSN, username, and password - and then attempt to open
it. Or could you do something like:
myODBCCon: ODBC://username:password@MyDSN/databasename
Query -
A holder for a SQL formatted query.
myQuery: make query
myQuery/SQL: "SELECT * FROM TABLE WHERE FIELD > 10"
Result -
A container that holds the results of an executed query
myResult: make result
myResult/SQL: myQuery
do myResult/Execute
And then, you could browse thru the result, pulling contents of fields,
etc.
- Porter
