SQLDriverConnect in unified ODBC

I have been off-line from the mailing list for a while - I was on holiday and didn't think I could cope with the mail load when I got back :-) So I've just retrieved this from the archive.... The DriverConnect option that I added for Empress basicaaly does change the directive based on the content of the DSN entry. It assumes that if there is a semicolon in the DSN entry then it must be a direct connect command - a simple logical database name would not contain a semicolon (would it?). This should work as suggested simply by removing the HAVE_EMPRESS directive. I added this as a directive because I understood that some ODBC interfaces didn't have this function. If, as Andreas seems to be suggesting, it is simply that it doesn't work correctly with some drivers, the directive could be removed. The DriverConnect command will only be issued if the DSN is of the correct format. Steve ----extract from archive--- > 2. Using SQLDriverConnect instead of SQLConnect. The decision would not > based on > compiler directive but the parameter string like "DSN=3Danydsn;". I do > not know > exactly how would be the best. The implementation from version 3.0.6 > try to apply something like what my imagination is. The method what =I > have implemented in the connect function is just a trial not a detailed= > and discussed solution. I didn't use SQLDriverConnect() due to a bug in the Adabas odbc library. The idea to decide which connect function to use depending on the parameter string sounds reasonable. >...... I think that the odbc stuff in general needs a rework, but I will wait for PHP4 before starting this. -Andreas -- = Andreas Karajannis GMD National Research Center for Information Technology Schloss Birlinghoven, D-53754 Sankt Augustin Phone +49 2241 142948 -----end of extract----- -- Steve Williams Interactive Media & Tools Group Empress Software Inc. http://www.empress.com