>I sent my delphi data conversion utility to my customer, and he couldn't
>even open the access files with it, getting the message Cannot load an
>IDAPI service library.
<snip>
>Help!

> I sent my delphi data conversion utility to my customer, and he couldn't
> even open the access files with it, getting the message Cannot load an
> IDAPI service library. The message also identified MSJT3032.DLL as the
> library in question.

> I read some things in FAQs, suggesting that DAO 3.0 needs to be on the
> machine with the application. But if the customer has installed the
> related VB4 application and the related VB6 application wouldn't the jet
> engine be installed already? Do I have to move some things around so
> Delphi or the BDE can see the jet engine?

> I tried rigging up a DAO 3.0 on another system here which had no other
> jet engines installed, and my data conversion utility still won't open
> the file, this time saying: General SQL error. Can't open a database
> created with a previous version of your application. But then why can I
> open it on my system? Why can the customer open it with his VB
> application?

> Help!

> To switch between the two use:
> BDE Administrator -> Configuration -> Drivers -> Native -> MSACCESS -> DLL32
> set to IDDAO32.DLL for DAO 3.0 and to IDDA3532.DLL for DAO 3.5

> "Bill Burns" <w...@rpinet.com> schreef in bericht
> news:390A01E6.1DBCBCD3@rpinet.com...
> > Here is my story.
> > I inherited an application which was developed in VB4.0 using a set of
> > Access databases, each containing a single table. Many customer problems
> > developed as we crossed into 2000, and so we updated them with a
> > somewhat revised version in VB6.0, but using the same access database
> > files. Still more problems, and, since I don't know VB, I thought I
> > would just rewrite it in Delphi 4 professional, then do a little data
> > conversion utility to move the data into dBase files and I would be down
> > to something I could at least chase when errors occur.
> > My data conversion utility runs fine on my system, converting a very
> > large set of Access files I borrowed from a customer. I had, at one
> > point, installed VB4 and VB6 on my system, and I also have Office 97
> > (with Access97) installed.

> > I sent my delphi data conversion utility to my customer, and he couldn't
> > even open the access files with it, getting the message Cannot load an
> > IDAPI service library. The message also identified MSJT3032.DLL as the
> > library in question.

> > I read some things in FAQs, suggesting that DAO 3.0 needs to be on the
> > machine with the application. But if the customer has installed the
> > related VB4 application and the related VB6 application wouldn't the jet
> > engine be installed already? Do I have to move some things around so
> > Delphi or the BDE can see the jet engine?

> > I tried rigging up a DAO 3.0 on another system here which had no other
> > jet engines installed, and my data conversion utility still won't open
> > the file, this time saying: General SQL error. Can't open a database
> > created with a previous version of your application. But then why can I
> > open it on my system? Why can the customer open it with his VB
> > application?

> > Help!

>I also learned (from Delphi FAQ4279B.txt) that ODBC must be installed in order
>to communicate between Delphi and Access.

> >Thanks for the help.

> >I also learned (from Delphi FAQ4279B.txt) that ODBC must be installed in
order
> >to communicate between Delphi and Access.

> I'm sorry but can someone confirm this. I've heard that Access can work