Delphi 6.01 patch and DataSnap (MIDAS) - New problems ?

[Philippe MAQUET]

I use MIDAS and DOA components (Direct Oracle Access) in a 3 tiers
application.

After having installed D6 patch 6.01 I noticed that:

1° TClientDataset.FetchParams does not retrieve its parameters correctly
anymore (DataType and/or ParamType are wrong), nor at design time neither at
run time.

2° TClientDataset.ApplyUpdates on a previously writable query gives error
message 'ORA-00904 invalid column name' if the query is multitable.

None of those happen before patch application.
As my DOA components for D6 did not change, I suspect the D6.01 patch.

So my question is. Does anyone using the BDE notice similar issues ?

Thank you for your help.

P. Maquet.

[Michel baily]

Dear Philippe,

Making some tests, I found that I have the same problem !
Still interested in a solution too,

Regards,

Michel Baily

"Philippe MAQUET" <p.ma...@co-link.be> wrote in message
news:3bc15e2e$1_2@dnews...

[Mark Horrocks]

> TClientDataset.FetchParams does not retrieve its parameters correctly
> anymore (DataType and/or ParamType are wrong), nor at design time neither
at
> run time.

Me too. I created a new RDM with a TIBQuery and set the params to
DataType : ftInteger
ParamType : ptInput.

In a new web broker app using TSocketConnector, FetchParams on an XMLBroker
returned
DataType : ftFMTBcd
ParamType : ptResult

Worse, on the day before I promised the board of my company that my project
would finally be on the net after nine months, I have destroyed my web
broker app twice today with a compile error as follows:-

[Error] RLINK32: Unsupported 16bit resource in file
"D:\Projects\Sportdata\Production\TestWeb\Unit1.DFM"

This has just happened for the second time. For now I will still be able to
see my components but after quitting Delphi and returning I will see an
error "Error in line 25, unable to build form" or similar.

I am using D6E, patch 1. I installed the patch yesterday. Since then I have
had windows memory errors on unloading the dll (in IIS5) followed by a
message saying runtime error 216. After that it will unload the dll.

It's been a bad day.

Mark Horrocks

[Mark Horrocks]

> [Error] RLINK32: Unsupported 16bit resource in file
> "D:\Projects\Sportdata\Production\TestWeb\Unit1.DFM"

I just changed the params on my xmlbroker to ftInteger and ptInput and my
web broker app compiled!

This is obviously what's wrong with my other app as well except many, many
more xmlbrokers to change params for. This is a total show stopper for me.
Can somebody please have a look at this problem for me? Thanks.

Mark Horrocks

[jkeegan]

1. Fetch Params -- we have just tested Fetch params using BDE and dbExpress and
found no problem getting the Param DataType. (We don't certify with DOA). If
you can give us a test case with BDE/ADO or dbExpress we will look at it
quickly.

I saw new postings on this issue noting a problem with XMLBroker. There appears
to have been no change in IBExpress or in DBClient to account for this. (In
dbExpress only, there has been a change where fields which used to be of type
BCD now show up as type FMTBcd; this was necessary because BCD field types are
actually TCurrency, with a maximum precision scale of 14.4. If you are using
IBExpress you will be affected by this.)

2. Concerning the Applyudpates issue with datasets that do not represent a
single table, the help describes how this is done. There has been no change in
this area.
In the table of Contents, Choose Developing Database Applications|Using
Provider Components|Applying Updates to datasets that do not represent a
single table. If you are doing this correctly, please send us a test case.

We are anxious to resolve these issues ASAP.

John Keegan

[Barry Mossman]

"jkeegan" <jke...@borland.com> wrote in message
news:3BC33105...@borland.com...

> I saw new postings on this issue noting a problem with XMLBroker.
There appears
> to have been no change in IBExpress or in DBClient to account for
this. (In
> dbExpress only, there has been a change where fields which used to be
of type
> BCD now show up as type FMTBcd; this was necessary because BCD field
types are
> actually TCurrency, with a maximum precision scale of 14.4. If you
are using
> IBExpress you will be affected by this.)

> We are anxious to resolve these issues ASAP.

I believe a project has been posted to binaries that demonstrates the
XmlBroker problem with get parameters. It does not involve BCD fields.
We see it with a normal integer parameter. This was broken by the
corrected 6.01 update.

Let us know if you need any further information.

Barry Mossman

[Mark Horrocks]

I have posted an app to attachments to demonstrate the bug.

The app comprises :-

1. App Server RDM. This contains one dataset provider, a TIBQuery and a
TIBTransaction.
Parameter Datatype for the query has been set to ftInteger and the
parameter type to ptInput.

2. Web Module, ISAPI Webbroker. This contains a TSocketConnector,
XMLBroker and InternetExpress Page Producer.

At design time, fetch params returns the wrong parameter types and won't
compile. Setting the parameter types to ftInteger and ptInput will allow the
app to compile. If it won't load, open the dfm file in notepad and edit the
properties for the first xml broker. Remove all the sanskrit you see there
where it should read ftInteger and ptInput.

Mark Horrocks

[Jim Elden]

Mark,

> I have destroyed my web
> broker app twice today with a compile error as follows:-
>
> [Error] RLINK32: Unsupported 16bit resource in file
> "D:\Projects\Sportdata\Production\TestWeb\Unit1.DFM"

I ran into the same problem in my client app when the parameters in
the App Server's datasets had values at design time. Clearing these
values solved this problem.

HTH,
Jim

[Mark Horrocks]

"Jim Elden" <x@yz> wrote in message news:3bc59799$1_2@dnews...

> I ran into the same problem in my client app when the parameters in
> the App Server's datasets had values at design time. Clearing these
> values solved this problem.

Thanks Jim,

I noticed that if I changed the param properties while still in desing mode,
it cleared the problem. If I had quit Delphi, it would not load the form
gain and that's where I was when I wrote the post. I got my app back by
editing the dfm file.

Mark Horrocks

[Philippe MAQUET]

> It does not involve BCD fields.
> We see it with a normal integer parameter. This was broken by the
> corrected 6.01 update.

Same in my tests with DOA : **Integer** parameters on server side are now
"fetched" as ftFMTBcd on client side. And ParamType is also changed from
ptInput to ptResult or ptInputOutput (depending on the number of parameters
fetched).

Philippe.

[Marilyn Thioux]

Hi Mark,

Thanks for the attachment. I see the problem and have entered it into Raid
(120423).

Thanks again,

Marilyn

[John Keegan]

We've reproduced this now -- we were originally testing with TDomConnection, which
seems to work fine. The problem occurs with TSocketConnection. I'll investigate,

Thanks,

John Keegan