Search found 301 matches

by Ludek
Fri 11 Jul 2014 15:14
Forum: SQL Server Data Access Components
Topic: Errror setting date value less then '01.01.1753'
Replies: 10
Views: 2414

Re: Errror setting date value less then '01.01.1753'

and do you use newest sdac? version 5 has problems...
by Ludek
Fri 11 Jul 2014 08:18
Forum: SQL Server Data Access Components
Topic: .recordcount invalid, when the query has too long record
Replies: 13
Views: 2391

Re: .recordcount invalid, when the query has too long record

We got reply, that our subscription already expired. have renewed, again asked for this version (already 2 days ago), until now no reply again :(
by Ludek
Wed 09 Jul 2014 08:16
Forum: SQL Server Data Access Components
Topic: Errror setting date value less then '01.01.1753'
Replies: 10
Views: 2414

Re: Errror setting date value less then '01.01.1753'

btw. if works for me fine, if there's a datetime2 column in the table being accessed (if sdac is new enough). datetime2 allows dates < 1.1.1753.
by Ludek
Wed 09 Jul 2014 07:57
Forum: SQL Server Data Access Components
Topic: Errror setting date value less then '01.01.1753'
Replies: 10
Views: 2414

Re: Errror setting date value less then '01.01.1753'

there's nothing, that devart people could do with this, as it is the limitation of sql server. see http://msdn.microsoft.com/en-us/library/ms187819.aspx
by Ludek
Mon 07 Jul 2014 06:18
Forum: SQL Server Data Access Components
Topic: .recordcount invalid, when the query has too long record
Replies: 13
Views: 2391

Re: .recordcount invalid, when the query has too long record

email sent last week also to [email protected], also no reply? contact form needs logging in and does not know any of possible emails, that we possibly used to register (it is already a long time ago, that the first sdac version was bought, perhaps registration info was lost?)
by Ludek
Fri 04 Jul 2014 12:09
Forum: SQL Server Data Access Components
Topic: .recordcount invalid, when the query has too long record
Replies: 13
Views: 2391

Re: .recordcount invalid, when the query has too long record

My colleague responsible for licensing products sent you an email 2.7. and today again, still without any response at all?!
by Ludek
Fri 27 Jun 2014 11:36
Forum: SQL Server Data Access Components
Topic: EDatabaseError 'Update failed. Found 2 records'.
Replies: 3
Views: 2344

Re: EDatabaseError 'Update failed. Found 2 records'.

I think you understand it perfectly :)
by Ludek
Wed 25 Jun 2014 15:28
Forum: SQL Server Data Access Components
Topic: .recordcount invalid, when the query has too long record
Replies: 13
Views: 2391

Re: .recordcount invalid, when the query has too long record

stupid question as always: when does this version come? if it is more than a week, would you mind telling us the fix in the 6.10.20 sources? (some line number & new version of the line?) i would be so happy :)
by Ludek
Tue 24 Jun 2014 14:16
Forum: SQL Server Data Access Components
Topic: .recordcount invalid, when the query has too long record
Replies: 13
Views: 2391

Re: .recordcount invalid, when the query has too long record

note: sdac 5.00.0.5 & delphi XE does NOT suffer from this bug. It is something new...
by Ludek
Tue 24 Jun 2014 14:05
Forum: SQL Server Data Access Components
Topic: .recordcount invalid, when the query has too long record
Replies: 13
Views: 2391

.recordcount invalid, when the query has too long record

delphi xe6 (both 32 and 64bit), newest sdac 6.10.20 (it happens also with .19)
steps:

1. create tmsquery with following sql text:

Code: Select all

with a as (
select
cast('' as varchar(255)) a,
cast('' as varchar(255)) b,
cast('' as varchar(255)) c,
cast('' as varchar(255)) d,
cast('' as varchar(255)) e,
cast('' as varchar(255)) f,
cast('' as varchar(255)) g,
cast('' as varchar(255)) h,
cast('' as varchar(255)) i,
cast('' as varchar(255)) j,
cast('' as varchar(255)) k,
cast('' as varchar(255)) l,
cast('' as varchar(255)) m,
cast('' as varchar(255)) n,
cast('' as varchar(255)) o,
cast('' as varchar(255)) p,
cast('' as varchar(255)) q,
cast('' as varchar(255)) r,
cast('' as varchar(255)) s,
cast('' as varchar(255)) t,
cast('' as varchar(255)) u,
cast('' as varchar(255)) v,
cast('' as varchar(255)) w,
cast('' as varchar(255)) x,
cast('' as varchar(255)) y,
cast('' as varchar(255)) z
)
select * from 
a a, 
a b, 
a c, 
a d,
a e,
a f,
a g,
a h,
a i,
a j,
a k,
a l,
a m,
a n,
a o,
a p,
a q,
a r,
a s,
a t,
a u,
a v,
a w,
a x,
a y,
a z,
sysobjects so
2. open it

3. examine the msquery.recordcount value

you'll get the number 5, although the query contains much more rows...

what can i do to get rid of this incorrect behavior?
Thanks, Ludek.
by Ludek
Wed 04 Jun 2014 13:58
Forum: SQL Server Data Access Components
Topic: .RecordCount in AfterFetch = 0?
Replies: 4
Views: 1456

Re: .RecordCount in AfterFetch = 0?

i can perhaps see the problem. in afterfetch is (when 2nd time opening the dataset) the dataset.state = dsinactive!
by Ludek
Wed 04 Jun 2014 13:41
Forum: SQL Server Data Access Components
Topic: .RecordCount in AfterFetch = 0?
Replies: 4
Views: 1456

Re: .RecordCount in AfterFetch = 0?

I can also see, that in .data.recordcount is the right value...