Re: Not enough storage space

Hello sardo007,

I have seen this problem happening as well. Closing or even destroying (releasing) the command objects does not seem to help (SQL CE 2.0). The only solution I have found that will help is to periodically close the data source and the session. This will actually release the memory or, as I experienced it, will put a ceiling on how much memory is used.

Regards,
João Paulo Figueira
eMVP

Hello, after searching this topic everywhere it seems nobody is facing
it the same way.

I'm developing an evc++ 4.0 database application using sqlce 2.0 and
oledb (adoce gave me some problems so I discarded it) Application
behaves well on every option, except one in which the user has to
introduce lots of data in a form. Data is selected from lists that are
populated with related data in other database tables. The form-filling
is OK, but after the user completes 10 or more forms the application
stops executing ICommands with the error "not enough storage to
complete this operation".

I've found this error in many places but they all seem to be
.NET-oriented. Since the target of my application is PocketPC 2003 and
even PocketPC 2002 (yes, there are still plenty of these all over
there) I can't use VC2005 to develop the application, so the problem
has to be solved using what I'm using (evc++4, sqlce2 and OLEDB) Every
solution I've found tells about Disposing the recordsets and commands,
but in the OLEDB interfaces I use there is no such Dispose method,
since they are all Released() as COM objects are.

The problem does not seem to be with the available storage memory
(there are more than 20MB of program space available and the
application has not been running long enough to fragment all that
space) It seems the sqlce dll or the oledb driver has some limit with
the memory used internally, since the problem occurs always after a
fixed form-filling sequence.

Any ideas are welcome. Thanks in advance.



.

Relevant Pages

  • Re: Not enough storage space
    ... I've tried to close the data source and the session, ... When I close the connection, the code I use is this: ... This will actually release the memory or, as I experienced it, ... oledb Application ...
    (microsoft.public.sqlserver.ce)
  • Re: Not enough storage space
    ... From my own experience the OLE DB provider will leak memory if you do not destroy all objects you created. ... When I close the connection, the code I use is this: ... oledb Application ...
    (microsoft.public.sqlserver.ce)
  • Re: Anyone know why the Alpha market is so so quiet?
    ... We noticed cron jobs were not getting run and cron was dying on their ... The bug was kicked up to AT&T. ... The cron was malloc'ing memory and never releasing it so it used up all ...
    (comp.os.vms)
  • Re: Memory problems (possibly very easy question)
    ... It is a common delusion that if you free storage your program should get smaller; ... memory usage warnings. ... But releasing it does not reduce the footprint, it merely keeps it from growing as the ... fragmentation may mean that the footprint will continue to grow, ...
    (microsoft.public.vc.mfc)
  • Re: Allocated Memory Alert
    ... Thanks for the advice, it doesn't seem to be releasing. ... I have run the Windows Update but there are no updates. ... > | A large amount of memory is committed to applications and processes. ...
    (microsoft.public.windows.server.sbs)