Devart Forums

Hi guys,

The following test works on Delphi 2009, but doesnt on Delphi 2010 using MSSQL Server 2005.

We have a table with a ntext field, now it can be any table but just for the exercise, I'm including the script of the table we are using:

CREATE TABLE [dbo].[SYSTEM_Template_Text](
[TemplateID] [int] NOT NULL,
[LanguageID] [int] NOT NULL CONSTRAINT [DF_SYSTEM_Template_Text_LanguageID] DEFAULT ((0)),
[Content] [ntext] NULL,
[Enabled] [bit] NOT NULL CONSTRAINT [DF_SYSTEM_Template_Text_Enabled] DEFAULT ((1)),
[Created] [datetime] NOT NULL CONSTRAINT [DF_SYSTEM_Template_Text_Created] DEFAULT (getdate()),
[CreatedBy] [int] NULL,
[Updated] [datetime] NULL,
[UpdatedBy] [int] NULL,
CONSTRAINT [PK_SYSTEM_Template_Text] PRIMARY KEY CLUSTERED
(
[TemplateID] ASC,
[LanguageID] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]


Now the problem is that if you do a normal client/server app, and read those values from the table it will return all the other values, but it will not return any data on the ntext field. The same situation will work with no problems on D2009.

We are using the latest driver version that supports D2010.

Any help, hot fix is highly appreciated.

Thank you for information. We have reproduced this problem and fixed it. This fix will be included in the next DbxSda build.

As a temporary solution you can set the SQLDataSet.MaxBlobSize property to 1.

Hi guys,

Thank you for the confirmation on the issue. I'm glad you guys fixed it. Now this hot fix will imply us adding this property change on looots of queries everywhere in our applications. So the question is, when can we expect this next build going out?

I will assume it is being taken as an urgent matter, because it is a very simple and straightforward case and a show stopper to anyone who uses Delphi 2010, due to the fact that NText is the default type for anything Unicode on MSSQL and Delphi 2010 is our unicode gateway to achieve unicode support.

Any updates on this matter will be highly appreciated. We use this in combination with ClientDatasets and so far in our try outs the hot fix doesnt solve the issue, we will keep trying to look at it, but it is important you guys take in consideration ClientDatasets on the mix. The same scenario, works in D2009.

We are planning to release the new build of DbxSda in two weeks.