🚀 go-pugleaf

The answer was given a week or so ago. Here is the answer.

Mark Johnson said:

-----------------------------------------------
I had this same problem.  The cause is the new tlb editor creates code with
a type IProviderPtr replacing  what used to be IProvider* in the generated
code.  If you go through all the generated source and replace IProviderPtr
with IProvider* the remote data modules will now work.  Hope this helps.

Mark Johnson
-----------------------------------------------


Panagiotis L. Staikos <pstaiko@ekt.gr> escribi� en el mensaje de noticias
37805D31.B7AF2946@ekt.gr...
> I have add at server Side (Remote DataModule)
> a TQuery Component and a TProvider(TProvider or TDataSetProvider)
> Component.
> I export the TProvider Component and it's DataSet property points to
> TQuery. The TQuery component has a SQL Statement.
> From Client Side i have a MIDAS, ClientDataset, DataSource, DBGrid
> Components.
> While i am connecting with my Server,when  i change the active property
> of The ClientDataSet to true
> (ClientDataSet Provider Property points to the Above TProvider)
> i get the Error :
> 'src->QueryInterface(GetIID(),(LPVOID*)(&intf))': No such interface
> supported
> @ C:\Program Files\Borland\CBuilder4\invlude\vcl\utilcls.h/2014
> Press [Y]es to terminate, [N]o to continue and [C]ancel to Debug.
>
> All the Providers from the server are shown in the drop-down list in the
> Provider property
> of the ClientDataSet Component!!!
>
> Prior the patch#1 i did't have any problem....
> More spesific the code that i use it works with C++Builder3, and
> C++Builder4 withou the path#1!!!
> How is the right connection between ClientDataSet and a Provider?
>
> I don't understand this error beacuse i think that all is ok.....
> (This problem was stop me since a week...)
> May i have a answer to this problem?
>
> Thanks. Panagiotis Staikos from Greece.
>
>
>


John Graham <jgraham@salts.navy.mil> escribi� en el mensaje de noticias
3791FB86.923BE652@salts.navy.mil...
> I converted a medium sized 2 tier app. into a 3 tier app using BCB 4 as
> installed from the factory.  The app. server contains a number of TQuery
>
> objects, and the client app. contains representative TClientDataSet
> objects.
>
> When compiled and linked, both client and server apps. worked great
> together.  However, when I installed the patch everything went south.  I
>
> have followed the threads in the forum about this problem, and have
> completely built a new server app. which runs and does its thing with
> the MS SQL database.  I have also recompiled the client app. The DCOM
> object fires up the app server which connects to the database normally.
> But when the client attempts to trigger one of the TQuery objects ( to
> find a record in a table ), I get a "No such interface supported" error
> and everything stops.
>
> The error is being caused by the call to the QueryInterface() function
> in line 2014 of the UTILCLS.H header file ( \include\vcl ), which is one
>
> of the files updated by the patch.
>
> I know if I uninstall BCB and reinstall it from the CD that the apps.
> will work.  I have done that once already.  But while both apps worked
> together when they were located on the same machine, I was unable to get
>
> the client to work with the app server with the server installed and
> running on one of our other servers ( an IBM NetFinity using NT Server
> as its OS ).  The client found and fired up the app server, but I was
> getting an OLE error number 80070105.  Yes, all required DLLs were
> installed and registered on the NF server, and the client's DCOM
> connection was able to connect.
>
> So I reinstalled the patch and landed square in the middle of the
> problem
> described in the first paragraphs above.
>
> Does anyone know what's going on?  I don't have any hair left to pull
> out!
>
> Regards,
> John
>
>