🚀 go-pugleaf

Thanks again,

I know quite well the distance between Montreal and Quebec, I've been hitch
inking there a few years ago...
Very beautiful country.

Well, back to the topic :
the driver ms access *.mdb is present in the drivers window (the odbc32 icon
in the config panel).
That's what's wierd...

Well, I guess we'll have to install mdac before launching the CD.

Do you know a method to detect if mdac is present or not (It would be better
not to install it each time the CD is inserted...as we have to restart the
computer after) without this f... message "interface not supported" ?

By the way, do you speak French ? ever been to France ?

Bye for now

Regards,

Jean Michel

"Rick Golden" <GoldenRick@hotmail.com> a �crit dans le message news:
3bf9675a_1@dnews...
> >>open a connection with the ADOConnection component :
> >>ConnectionString field : DRIVER={microsoft access driver (*.mdb)};
> >>DBQ=Mybase.mdb
> >>Provider field : MSDASQL
> >>Connected field : false
>
> So you are using ADO.. and of course at least one version must be present
in
> the client system..
>
> You can rely on Windows ME, XP and I think 2000 to have at least one
version
> installed...
> but if not you must install it. because if it's not there at all, of
course
> you'll get this kind of error.
> because it is an ActiveX and you cannot create and use one of it's
interface
> it is absent...
>
>
> >>It works on all the computers here.
> >>But not at the customer's, who has a "client access odbc driver 32 bit"
in
> >>>>the odbc driver window, which we don't have.
> >>(he is linked to a AS/400 where others databases are stored).
> >>message : "interface not supported".
>
>
> if the driver you specifying in DRIVER is not there then the connection
will
> not work.
>
> >>we are not even able to re-create the problem here (and our customer is
in
> >>avignon, and we are in saint etienne, if you know France (about 250 Km))
>
> about the distance between Montreal-Quebec (if you now Canada about 253
Km)
> not very far but far enough to be disturbing....
>
> Maybe you have your reasons, but why aren't you using an ADO driver
> specifically for ms-access, so you will
> no longer need to use ODBC at all.....
>
> you can find it (if you want to try it)
>
> http://www.microsoft.com/data/download_260rtm.htm
> http://www.microsoft.com/data/download_Jet4SP3.htm
>
>
> good luck
>
>
> Jean Michel <jm@magcom.fr> wrote in message news:3bf93204_1@dnews...
> > Hi,
> >
> > Thanks for helping...
> >
> > Here is what we do (or try to) :
> >
> > open a connection with the ADOConnection component :
> > ConnectionString field : DRIVER={microsoft access driver (*.mdb)};
> > DBQ=Mybase.mdb
> > Provider field : MSDASQL
> > Connected field : false
> >
> > to perform a query, we use the ADOQuery component like this :
> > ADOQuery->SQL->Add ("select*...");
> > ADOQuery->Open();
> > while
> > etc...
> >
> > It works on all the computers here.
> > But not at the customer's, who has a "client access odbc driver 32 bit"
in
> > the odbc driver window, which we don't have.
> > (he is linked to a AS/400 where others databases are stored).
> > message : "interface not supported".
> >
> > Installing mdac2.6 and restart computer->it works !
> >
> > we are not even able to re-create the problem here (and our customer is
in
> > avignon, and we are in saint etienne, if you know France (about 250 Km))
> >
> > any hints ?
> >
> > Thanks
> >
> > Jean Michel
> >
> >
> > "Rick Golden" <GoldenRick@hotmail.com> a �crit dans le message news:
> > 3bf9152d_2@dnews...
> > >
> > > First question Why are you using ODBC... there is a good MS-Access
> driver
> > > for ADO?
> > >
> > > Are you sure your not using the BDE?
> > >
> > >
> > >
> > > Jean Michel <jm@magcom.fr> wrote in message news:3bf8e250_2@dnews...
> > > > Hi,
> > > >
> > > > Thanks for the answer.
> > > >
> > > > We are using a Ms access database, on a odbc connection (classic ms
> > driver
> > > > declaration)
> > > >
> > > > How do you make a "silent" install of ado ? (refer to : so it should
> be
> > > > installed)
> > > >
> > > > The Drivers seem to be installed.
> > > >
> > > > an other driver is installed : client access odbc drivers 32 bit
> > > > on all the computers on which we get the "interface not supported"
> > > message.
> > > >
> > > > Has anyone ever have this problem ?
> > > >
> > > > Do you know how to install MDAC without restarting the computer ?
> > > > Or to test if the mdac is allright before installing it ?
> > > >
> > > > any other solution than installing MDAC ?
> > > >
> > > > Thanks
> > > >
> > > > Jean Michel
> > > >
> > > >
> > > > "Rick Golden" <GoldenRick@hotmail.com> a �crit dans le message news:
> > > > 3bf3d8d1_2@dnews...
> > > > > your application seems to use ADO
> > > > >
> > > > > so it should be installed??
> > > > >
> > > > > Quel BD utilisez vous?
> > > > > Quel service d'ADO ?????
> > > > >
> > > > > Il faut surement installer les pilotes que vous utilisez
> > > > >
> > > > > Bonne chance
> > > > >
> > > > >
> > > > >
> > > > > Jean Michel <jm@magcom.fr> wrote in message
> news:3bf3938d$1_2@dnews...
> > > > > > Hi everybody,
> > > > > >
> > > > > > We are developping a small application using c++builder.
> > > > > > Problem : on all the computers here, it works
> > > > > > at the customer's place, it doesn't. Message : Interface not
> > > supported.
> > > > > > after installing mdac2.6, it works
> > > > > >
> > > > > > any idea ?
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Jean Michel
> > > > > > (from France)
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>