Hi,

Have a client who imported a picture into a blob field of around 20Mb.  The
server engine reported an 'Out Of Memory' error on OPENBLOB.  Should this
happen?  Is a 20Mb blob indeed too large to open in a client-server
environment?  DBISAM V3.30

Thanks

Alex

Anyone have anything on this?  Are there any realistic limitations or things
to watch out for?  We did do some maintenance ont hat file ofr this client
(predominantly reducing these picture sizes ) and the issues did disappear.

Thanks

Alex
"Al Vas" <noreply@noreply.com> wrote in message
news:7C762466-427F-4E31-94CA-58123BA53855@news.elevatesoft.com...
> Hi,
>
> Have a client who imported a picture into a blob field of around 20Mb.
> The server engine reported an 'Out Of Memory' error on OPENBLOB.  Should
> this happen?  Is a 20Mb blob indeed too large to open in a client-server
> environment?  DBISAM V3.30
>
> Thanks
>
> Alex

Alex,

<< Have a client who imported a picture into a blob field of around 20Mb.
The server engine reported an 'Out Of Memory' error on OPENBLOB.  Should
this happen?  Is a 20Mb blob indeed too large to open in a client-server
environment?  DBISAM V3.30 >>

You really need to consider moving to DBISAM 4.x.  All of these issues that
you're running into have either been fixed in 4.x, or are no longer an issue
due to design changes.  We are simply not going to be doing any more fixes
for 3.x, so most of the time I won't be able to help you at all.

The above issue is due to the default memory manager in Delphi combined with
(most likely) too small of a BLOB block size, so it can be corrected if you
recompile the DBISAM Server with FastMM4 and increase the BLOB block size
for the table.  What is the BLOB block size setting for the table ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim,

You're preaching to the converted.  I know we have to change to V4.  It's
just unfortunately not that simple for us due to the SQL syntax changes
(which means a 100% top-to-bottom testing process).  We have not only client
application but associated utilities, web-browser application changes,
third-party considerations, conversion of all clients in a limited timeframe
and so on.  We have earmarked a 3 month timeframe to perform this and it is
a matter of us finding breathing space in our development schedule to do
this (not that easy).  Not asking for fixes to V3 just wanting to know what
might cause it and you have answered that well.  Thanks again.

Alex

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:95EA80C6-CFEA-4F09-B83A-A87C3394A9A3@news.elevatesoft.com...
> Alex,
>
> << Have a client who imported a picture into a blob field of around 20Mb.
> The server engine reported an 'Out Of Memory' error on OPENBLOB.  Should
> this happen?  Is a 20Mb blob indeed too large to open in a client-server
> environment?  DBISAM V3.30 >>
>
> You really need to consider moving to DBISAM 4.x.  All of these issues
> that you're running into have either been fixed in 4.x, or are no longer
> an issue due to design changes.  We are simply not going to be doing any
> more fixes for 3.x, so most of the time I won't be able to help you at
> all.
>
> The above issue is due to the default memory manager in Delphi combined
> with (most likely) too small of a BLOB block size, so it can be corrected
> if you recompile the DBISAM Server with FastMM4 and increase the BLOB
> block size for the table.  What is the BLOB block size setting for the
> table ?
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Alex,

<< You're preaching to the converted.  I know we have to change to V4.  It's
just unfortunately not that simple for us due to the SQL syntax changes
(which means a 100% top-to-bottom testing process).  We have not only client
application but associated utilities, web-browser application changes,
third-party considerations, conversion of all clients in a limited timeframe
and so on.  We have earmarked a 3 month timeframe to perform this and it is
a matter of us finding breathing space in our development schedule to do
this (not that easy).  Not asking for fixes to V3 just wanting to know what
might cause it and you have answered that well.  Thanks again. >>

I understand.  I just feel very unhelpful when not being able to arrange for
a fix when you encounter issues.  The problem is that if I went back and
tried to correct 3.x right now, I'd most likely make the problem worse, not
better.  The other issue is that we do *not* have 3.x in our automated
testing system, so it is impossible for us to regression test any changes to
3.x.

--
Tim Young
Elevate Software
www.elevatesoft.com