Icon View Thread

The following is the text of the current message along with any replies.
Messages 11 to 13 of 13 total
Thread kbmmw / EDB setup problems
Tue, Oct 23 2007 3:48 AMPermanent Link

"Harry de Boer"
Eryk,

Allright. I understand. Altough your 'guesses' have been proven right in the
past I 'guess' Smile
Thanks anyway. I hope your guesses steers us in te right way for solving
this.

Regards, Harry

"Eryk Bottomley" <no@way.com> schreef in bericht
news:8F042EFF-3C27-4025-9FDA-46A2DA2058AA@news.elevatesoft.com...
> Harry,
>
> > I see. I will contact Kim (Components4Developers - kbmmw) Madsen with
this
> > info,
>
>
> I would class it as "wild speculation" rather than "info". I don't use
> either ElevateDB or the memtable stuff ...I'm just making a guesses
> based on general principles.
>
> Eryk

Tue, Oct 23 2007 1:56 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Harry,

<< Well no, not quite. It is a simple 'select * from aanhef' statement,
nothing fancy about it. 'Aanhef'  is a table with two fields and 82 rows.
The error occurs because a temp table seems to be made and it exceeds the
max limit for a file. The strange thing is that it don't happen with EDBmngr
but from the testapps (client and server) that comes with kbmmw 2.8.0 the
error occurs. This takes already more then a day of my time and it's driving
me mad :0 (well no, not really ofcourse, I'm still making sense I hope), but
I want to start a project (kbmmw/dbisam replacement) -planned start is
tommorow Frownand this is stopping me from further development right now. Do
you have any idea what can cause this error? >>

Make sure that you set the RequestSensitive property to True, and that
should solve the problem.  The issue is most likely the bug in the current
version whereby insensitive result sets keep refreshing, causing many more
rows to be generated than necessary.  This will be fixed in 1.06, which is
very close to release.

--
Tim Young
Elevate Software
www.elevatesoft.com

Wed, Oct 24 2007 4:13 AMPermanent Link

"Harry de Boer"
Tim,

> Make sure that you set the RequestSensitive property to True, and that
> should solve the problem.  The issue is most likely the bug in the current
> version whereby insensitive result sets keep refreshing, causing many more
> rows to be generated than necessary.
Ok. Didnot know such a bug existed.

>This will be fixed in 1.06, which is very close to release.
Great

Regards, Harry


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht
news:0FA7BB70-C458-41FF-B07A-5E2EF5B31F51@news.elevatesoft.com...
> Harry,
>
> << Well no, not quite. It is a simple 'select * from aanhef' statement,
> nothing fancy about it. 'Aanhef'  is a table with two fields and 82 rows.
> The error occurs because a temp table seems to be made and it exceeds the
> max limit for a file. The strange thing is that it don't happen with
EDBmngr
> but from the testapps (client and server) that comes with kbmmw 2.8.0 the
> error occurs. This takes already more then a day of my time and it's
driving
> me mad :0 (well no, not really ofcourse, I'm still making sense I hope),
but
> I want to start a project (kbmmw/dbisam replacement) -planned start is
> tommorow Frownand this is stopping me from further development right now. Do
> you have any idea what can cause this error? >>
>
> Make sure that you set the RequestSensitive property to True, and that
> should solve the problem.  The issue is most likely the bug in the current
> version whereby insensitive result sets keep refreshing, causing many more
> rows to be generated than necessary.  This will be fixed in 1.06, which is
> very close to release.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

« Previous PagePage 2 of 2
Jump to Page:  1 2
Image