Devart Forums

I did what you said and worked.
But I need to add a LIBSUFFIX on my unidac projects.
With LIBSUFFIX the providers didn't appears on component pallete.

What would it be?

I'm building unidac packages but when I install the packages, the provider components didn't appears on delphi 7 component pallete. The others components are there but the providers didn't. The provider's pallete is not created.

I'm building in following order, from command line:

Unidac\Source\Delphi7\oraprovider70.dpk
Unidac\Source\Delphi7\ibprovider70.dpk
Unidac\Source\Delphi7\myprovider70.dpk
Unidac\Source\Delphi7\msprovider70.dpk
Unidac\Source\Delphi7\pgprovider70.dpk
Unidac\Source\Delphi7\liteprovider70.dpk
Unidac\Source\Delphi7\odbcprovider70.dpk
Unidac\Source\Delphi7\accessprovider70.dpk
Unidac\Source\Delphi7\db2provider70.dpk
Unidac\Source\Delphi7\adsprovider70.dpk
Unidac\Source\Delphi7\dac70.dpk
Unidac\Source\Delphi7\dacvcl70.dpk
Unidac\Source\Delphi7\dcldac70.dpk
Unidac\Source\Delphi7\unidac70.dpk
Unidac\Source\Delphi7\unidacvcl70.dpk
Unidac\Source\Delphi7\dclunidac70.dpk

It's 3.70 version of Unidac.

Can you help me?

I'm perform a query on a sql server table with more than 269,993 records.

In this query I use LIKE statements and it take only "00:00:00.086" (less than 1 second) to run.

If I add some comment before this, the time jumps to "00:00:08.639" (almost 10 seconds).

I use fetchAll = false. If it's true then works fine.

My current version of Unidac is 3.60.0.15.


Can You help me?

Ok,
Thanks!.

But before unidac update it works.
Why?

SQL Server.

After update unidac to 3.60.0.15 version we cannot access LargeInt field with Value property. Instead we have to do AsInteger to work.

If we use Table.FieldByName('LargeIntField').Value it raises "Cannot access field 'LargeIntField' as type Variant" error.

On prior version (3.0.0.9) it's not happened.

Thanks,
When the version will be released?

I try to connect a nexusdb table with unitable but when the table is opened, it's raising an error message "Option 5 not supported".
This error happens when i have string fields with size less than 32.

Example:

CREATE TABLE TEST (ID INTEGER) >>> raise an error
CREATE TABLE TEST_2(ID INTEGER, CODE VARCHAR(31)) >>> raise an error

CREATE TABLE TEST_3(ID INTEGER, CODE VARCHAR(32)) >>> works fine

If I try to open the same table with TTable or TADOTable it's works too.

Could you help me?

I already find out how to do it.
Thanks!!!!!

I have some tables with autoinc fields. When I open a table with autoinc field, the field is fetched as integer field.
How can I fetch de correct information about these fields?

I try to use TuniMetadata with SQLServer 2008 to retrieve indexes information.

It works fine, but I need the schema information too, because I have tables on different schemas that I created.

When I get the Indexes metadata information, the field SCHEMA_TABLE from TUniMetadata is empty when the table belongs to schema that I created.

Debugging the source code, I found that the error is the "user_name" function on statement that fecth index information.

I use the same statement with "schema_name" and works fine.

SQLServer have been support schema since 2005 version.

It's happening on 3.00.0.7 version too.

Tobias,
I decide to work with schemas on SQLServer. Instead of spread tables among many databases, i will keep it on one database and put them on different schemas.
It solve my problem.

Thanks!

thanks!!!

I try using uniMetadata with Postgre.
I have one index with "DESC" sorted field.
When I try to get the Descending Value from uniMetadata with IndexColumns Restrictions, it gives me 0 in descending column.

What can I do?