>Expected: DataAccessSql should only be assumed if a class is NOT specified (or String.Empty). If the class is not recognized then an exception should be thrown

> by design...in fact if you completely leave the specification out of the .config file it will also assume SQL Server data access.

Wouldn't the dataAccessClassName come in as String.Empty or null in this case? I'm talking about a SPELLING MISTAKE. No error is raised, it just uses the wrong provider and crashes later.

> Actually, CreateDataAccessObject() is eventually in the call chain.

Not in MM 2.4 - the decision as to which data access class should be instantiated has been made by then.

> are you trying to access Postgres data?

No, MYOB (accounting package which is pretty ubiquitious in NZ & Aust). Only an ODBC driver is available, not much chance of OLE-DB or anything else in the near future: database is in a proprietary format.

I've got it reading. Not too fussed on getting the BLG or anything fancy to work although I will need to do inserts and other commands. However the MYOB driver is a bit oddball here so I'm not sure how generically ODBC this bit will be.