Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!purdue!haven.umd.edu!hecate.umd.edu!bloom-beacon.mit.edu!news.mathworks.com!cam-news-hub1.bbnplanet.com!news.bbnplanet.com!su-news-hub1.bbnplanet.com!arclight.uoregon.edu!news.bc.net!torn!news!poonc
From: poonc@uwindsor.ca (Poon  Bruce)
Subject: Question: why are certain ODBC drivers incompatible?
X-Nntp-Posting-Host: server.uwindsor.ca
Message-ID: <E248rz.n1o@news.uwindsor.ca>
Sender: news@news.uwindsor.ca (Usenet)
Organization: University of Windsor
Date: Sun, 8 Dec 1996 22:21:35 GMT
Lines: 20

Hi everyone..

I got a question regarding ODBC drivers.  From what I read about these
drivers, they have a number of compliance levels.  The newest Paradox ODBC
desktop driver from Microsoft (version 3.0) cannot update with VA for
some reasons (refer to my other post), but the Access/Excel drivers work
perfectly. I am doing a project, and I like to give my evaluators a
rational explaination why this occurs.  Can any one please give me one? 

I also know that Microsoft creates a set of ODBC drivers that only work
for the Microsoft Office suite.  I thought the point of ODBC is that
application developers can access database by accessing one common API
(the ODBC driver manager).  So, why won't these drivers work for other
application?  I'm confused.. some please help me out :)

Thanx!

Bruce


