EDB record limits and EDB vs RAPI

Two simple questions:

1. Im insterting records in a recently created EDB databse for WM 5.0, but only 16 records can be witten, does any body knows where is the property to accept more than only 16 records?

2. is there ann RAPI for manage EDB. because my aplication use a lot the RAPI that comes for CEDB, but what about EDB? does it exist?

The answer to the second part of the question is that RAPI support for EDB is not yet there.

For the first question, I would like to see the code that you are using to write the records.

Thanks.

EDB record limits and EDB vs RAPI

Two simple questions:

1. Im insterting records in a recently created EDB databse for WM 5.0, but only 16 records can be witten, does any body knows where is the property to accept more than only 16 records?

2. is there ann RAPI for manage EDB. because my aplication use a lot the RAPI that comes for CEDB, but what about EDB? does it exist?

The answer to the second part of the question is that RAPI support for EDB is not yet there.

For the first question, I would like to see the code that you are using to write the records.

Thanks.

Easy way to find connection leaks?

I, just like others, am experiencing problems with data leaks. I was wondering if anyone knows of a tool out there that can help pinpoint the pages with problems? I basically want to find the culprits!

Thanks,
--
YonahBack in the old days I usedNumega's BoundsChecker but it's for C++.

In principal with managed code (i.e., C# and VB.Net) you shouldn't have problems with memory leaks, though I'm sure there are ways to generate them.

There may be some tricks you can use to recover memory faster. The articles below may help:

Garbage Collector Basics and Performance Hints

Garbage Collection: Automatic Memory Management in the Microsoft .NET Framework|||::In principal with managed code (i.e., C# and VB.Net) you shouldn't have problems with
::memory leaks.

Interesting statement given that the question is for CONNECTION LEAKS, not memory leaks. The articles are of similar relevance :-(

I, just like others, am experiencing problems with data leaks.

No, not really.

What you can do is get a profiler (there are some good free ones around) that helps you to figur out what objects are in memory and why. If you experience a "forgot to close the connection" issue, though - you are stuck here.

What I do in general (in our O/R mapper) is handle all database connection open/close from one class - so I actually never have this issue, simply because my code is very sure things are easy here. Consider going this appraoch, concentrating this in one location.

Besides this:

You an set for SQL Server an application "name" that shows up in SQL Server's enterprise manager when you look at open connections. You COULD set this name differently for every page (like the page name), then you would know WHERE you forget to close the connection.