Not enough Memory BDE Error 
Author Message
 Not enough Memory BDE Error

It's been a very bad Delphi day at the office.

[Delphi 2.0, BDE, Paradox 7]

Our developing application has started getting "Not enough memory to
perform this operation" errors from the BDE some of the time, and
Access violations at other times.

To help isolate the problem, we started a NEW application with
one totally blank form and one data module. NO CODE AT ALL.

We started adding TQuery components to the DataModule. Each one
was set to its defaults with SQL like:

  select [field list] from tablename

None of the tables had over 52 records in it, most much smaller.

I added 52 Queries (all different tables) and then started over
adding Queries and setting Activate to TRUE. When I hit table
67, I ran out of memory, and if I ran the application I got
Access Violations.

I tried doubling all the parameters on the SYSTEM tab of the BDE
configuration and it still bombed trying to open Query # 67.

In our actual application, we don't have this many Queries open
at one time, but the queries are often parameterized and there are
many data aware components including bunches of TDBLookupComboBoxes.

During all this testing, low memory free was over 500 K, and VM
over 140 meg.  USER and GDI memory were over 60% free.

I paid some money to the Borland Guy, but he didn't have a clue.

--

http://www.***.com/ ~kwdavids/

* In this world of toil and sin
  Your scalp grows bald, but not your chin. - Burma Sig



Mon, 22 Feb 1999 03:00:00 GMT
 Not enough Memory BDE Error

Quote:

> It's been a very bad Delphi day at the office.

> [Delphi 2.0, BDE, Paradox 7]

> Our developing application has started getting "Not enough memory to
> perform this operation" errors from the BDE some of the time, and
> Access violations at other times.

> To help isolate the problem, we started a NEW application with
> one totally blank form and one data module. NO CODE AT ALL.

> We started adding TQuery components to the DataModule. Each one
> was set to its defaults with SQL like:

>   select [field list] from tablename

> None of the tables had over 52 records in it, most much smaller.

> I added 52 Queries (all different tables) and then started over
> adding Queries and setting Activate to TRUE. When I hit table
> 67, I ran out of memory, and if I ran the application I got
> Access Violations.

> I tried doubling all the parameters on the SYSTEM tab of the BDE
> configuration and it still bombed trying to open Query # 67.

> In our actual application, we don't have this many Queries open
> at one time, but the queries are often parameterized and there are
> many data aware components including bunches of TDBLookupComboBoxes.

> During all this testing, low memory free was over 500 K, and VM
> over 140 meg.  USER and GDI memory were over 60% free.

> I paid some money to the Borland Guy, but he didn't have a clue.

> --

> http://www.interpath.com/~kwdavids/

> * In this world of toil and sin
>   Your scalp grows bald, but not your chin. - Burma Sig

Kevin,

Good Luck, you might try to free up some memory by using the following:
  FreeLibrary(GetModuleHandle('OLEAuto32'));
I assume you are using Delphi 2.0. This routine frees about 1 meg of
memory and can be used if your application does not use OLE.

I read about this on the news group and apparently Delphi indirectly
loads OLE support automatically, even if you don't need it.

As to your queries, I assume you already know - close, prepare, open
then close as needed by your application. Select only fields needed, use
a where to limit records returned, etc.

I have been using ODBC to MSSQL Server and am also having a Bad Delphi
day with EAccess Violations - randomly when I rerun a search query with
new parameters. Someone said Borland has bugs in their ODBC connections,
I don't know but something weird is happening.

Good Luck,

Austin



Tue, 23 Feb 1999 03:00:00 GMT
 Not enough Memory BDE Error

Austin McCracken wrote in a message appearing on comp.lang.pascal.delphi.databases:

Quote:
>As to your queries, I assume you already know - close, prepare, open
>then close as needed by your application. Select only fields needed, use
>a where to limit records returned, etc.

IS the BDE all that fragile? I have huge amounts of Windows memory free
but get Insufficient Memory from the BDE.

Unfortunately, there are many TDBLookupComboBoxes in the application
requiring queries to be left open.

I've been in data processing for 20 years and I've worked under some
severe memory constraints in the past. But really, I THOUGHT the bad
ole days were over. I've run MUCH MORE COMPLEX applications in COBOL
under MS-DOS.

--

http://www.interpath.com/~kwdavids/

* My paradigm doesn't shift like it used to.



Thu, 25 Feb 1999 03:00:00 GMT
 
 [ 3 post ] 

 Relevant Pages 

1. Not enough memory/Virtual memory error from large query

2. BDE - failure (not enough memory)

3. Error msg: Not enough memory...

4. Not enough memory error.

5. PDOXW5 COMPILER ERROR "NOT ENOUGH MEMORY"

6. error - There is not enough memory to complete operation

7. Errors on linux, not enough memory?

8. Error Message "Not Enough Memory"

9. ERROR: 17803 - not enough memory

10. Not enough memory error

11. Not enough memory error on ontape -r

12. HELP: Not enough memory to increase memory!


 
Powered by phpBB® Forum Software