Devart Forums

Hello,

I am using dbexpsda.dll and all the fields appears as NOT required.

This bug is not link to a specific version of Sql Server it´s just a design problem of the dll.

I have the same problem with the driver of Oracle and it appears that this will be fixed in the next release.

Thanks

Setting flag isNullable = False (Required = True) causes problems with editing queries that include autoincrement fields (NOT NULL AUTO_INCREMENT) or NOT NULL fields with DEFAULT VALUE.

> I have the same problem with the driver of Oracle and it appears that this
> will be fixed in the next release.

We'll discuss this issue.

If there are problems with editing querys, Required = True and Autoincrement or Default Value fields, Core Labs has 3 options:

1- Fix this problem (i don´t known if it is possible)
2- Set Required = False in this kind of fields
3- Warn the user to set it to False in this kind of fields.

But I think that the solution of Set = False in ALL fields in not a good solution.

Thanks in advance

> 1- Fix this problem (i don´t known if it is possible)

This code is Borland one and we are unable to change this behaviour.

> 2- Set Required = False in this kind of fields

Getting a list of fields with DEFAULT VALUE requires an additional reference to the server that causes performance loss.

> 3- Warn the user to set it to False in this kind of fields.

It's not acceptable especially for users who use our driver for several years.

Now we are considering a possibility of adding an additional option setting that will set IsNullable flags.

It could be a good solution, but anyway there must be an "automatic option", now i have to set the required in every DataSet!

Thanks a lot.

I have scanned the dbExpress driver for SQL Server History, and I notice that the IsNullable Solution has not been built into the driver, or has it been put into the driver and not documented.

all I am wanting to know is has this problem been adressed, or is it still been considered as a possibility, or has it slipped off the radar since Wed Mar 02, 2005 6:33 pm.

Hey I have the same problem -> how do i find out if field is required or not (i.e. not null).

Is this bug ever going to be fixed or an extra property made to find out what the field status is?

This functionality will be added in the next build of DbxSda (3.10.6). It will be available in about one week.
Please watch for announcements at the forum.

thanks EvgeniyM, Just one more quick question we are using 2.50.5 currently, will we have access to 3.10.6 or will this require additional purchasing

You will be able to download DbxSda 3.10.6 and next versions of DbxSda 3 only after purchasing Version Upgrade.

Surely u mean 3.00.6 or is the revision higher?

Next build of DbxSda (3.10.6) will be available in the nearest few days. I mean, if you become registered user of DbxSda 3 you will be able to download this build and future builds of DbxSda 3.