Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 26 total
Thread ADO.NET
Wed, May 30 2007 7:02 AMPermanent Link

tomas
Hi,

I am registered user of DBISAM and I need to develop ASP.NET(BDS2006) front end for our desktop app.
There is no way to bring DBISAM to ASP.NET(I am not counting ODBC drivers because they are not stable on ASP.NET
and producing errors) so one choice is to move to elevatedb because it will support ADO.NET. Question is when ADO.NET will be avaible?

Regards,
Tomas
Wed, May 30 2007 9:36 AMPermanent Link

"Jose Eduardo Helminsky"
Tomas

See the thread "VCL.NET" posted in May 26 by Tim

Eduardo

Wed, May 30 2007 11:52 AMPermanent Link

Michael Baytalsky
Hi Tomas,

I don't mean to undermine your decision to switch to ElevateDB, cause
it's probably your best choice in the long run, but for know (and for
awhile) we've had ADO.Net provider for DBISAM 3&4.
Look here:
http://www.contextsoft.com/products/dbisamnet/
Downloads:
http://www.contextsoft.com/products/dbisamnet/downloads.jsp

So you can begin developing (learning) using ADO.Net now and then
switch to elevatedb later.

Sincerely,
Michael

tomas wrote:
> Hi,
>
> I am registered user of DBISAM and I need to develop ASP.NET(BDS2006) front end for our desktop app.
> There is no way to bring DBISAM to ASP.NET(I am not counting ODBC drivers because they are not stable on ASP.NET
> and producing errors) so one choice is to move to elevatedb because it will support ADO.NET. Question is when ADO.NET will be avaible?
>
> Regards,
> Tomas
>
Wed, May 30 2007 1:12 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Tomas,

<< I am registered user of DBISAM and I need to develop ASP.NET(BDS2006)
front end for our desktop app.
There is no way to bring DBISAM to ASP.NET(I am not counting ODBC drivers
because they are not stable on ASP.NET and producing errors) so one choice
is to move to elevatedb because it will support ADO.NET. Question is when
ADO.NET will be avaible? >>

What specifically are you having an issue with regarding the ODBC driver ?
The DBISAM ODBC driver should work just fine with ASP.NET using the ODBC.NET
data provider.

Please see this thread for more information on the ADO.NET data provider for
ElevateDB:

http://www.elevatesoft.com/scripts/newsgrp.dll?action=openmsg&group=16&msg=1953&page=1

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Jun 1 2007 2:30 AMPermanent Link

tomas
"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Tomas,

<< I am registered user of DBISAM and I need to develop ASP.NET(BDS2006)
front end for our desktop app.
There is no way to bring DBISAM to ASP.NET(I am not counting ODBC drivers
because they are not stable on ASP.NET and producing errors) so one choice
is to move to elevatedb because it will support ADO.NET. Question is when
ADO.NET will be avaible? >>

<<<What specifically are you having an issue with regarding the ODBC driver ?
The DBISAM ODBC driver should work just fine with ASP.NET using the ODBC.NET
data provider.>>>

After executing several queries from ASP.NET we get error below(in event viewer) and ASP.NET app stop respoding.

Event Type:   Error
Event Source:   COM+
Event Category:   Unknown
Event ID:   4786
Date:      1/11/2007
Time:      2:19:31 PM
User:      N/A
Computer:   RM-005-18
Description:
The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the
information below.
Component Prog ID: 0[ODBC][Env 7f423b8]
Method Name: IDispenserDriver::DestroyResource
Process Name: w3wp.exe
Exception: C0000005
Address: 0x0D8D81E0
Call Stack:
dbodbc! + 0x81e0
dbodbc! + 0x279a
dbodbc! + 0x3073
dbodbc! + 0x148faf
ODBC32SQLAllocConnectt + 0x988
ODBC32SQLDisconnectt + 0x426
ODBC32SQLConnectAA + 0x17be
comsvcs!DispManGetContext + 0xd10
comsvcs!DispManGetContext + 0xff1
comsvcs!DispManGetContext + 0x210e
ODBC32SQLConnectAA + 0x1fa0
ODBC32SQLConnectAA + 0x28d1
ODBC32SQLSetEnvAttrr + 0x230a
+ 0xd270296
+ 0xe8f837b
mscorwks!CorExitProcess + 0x1d070
mscorwks!CorExitProcess + 0x1d132
mscorwks!GetCompileInfo + 0x3346
mscorwks!ReleaseFusionInterfaces + 0x384c3
mscorwks!CorMarkThreadInThreadPool + 0x4d82
mscorwks!GetCompileInfo + 0x2824a
mscorwks!Ordinal77 + 0x989e
mscorwks!CoInitializeCor + 0x5c25
kernel32!GetModuleFileNameA + 0xeb
Fri, Jun 1 2007 3:25 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Tomas,

<< After executing several queries from ASP.NET we get error below(in event
viewer) and ASP.NET app stop respoding. >>

And are you using the ODBC.NET data provider, or some other data provider ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Sat, Jun 2 2007 9:01 AMPermanent Link

Chris Holland

SEC Solutions Ltd.

Avatar

Team Elevate Team Elevate

I have seen this problem as well.

Rapidly connecting and disconnecting can cause strange errors.
I thought it might be something to do with the garbage colection in .NET

If you do something like this:

for(int i = 0; i < 100; i++)
{
  Connect();

  .. do something here

  Disconnect();
}

It quite often throws an error.

However this:

Connect();

for(int i = 0; i < 100; i++)
{
  .. do something here
}

Disconnect();

Works fine.

Chris Holland
Mon, Jun 4 2007 3:13 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Chris,

<< I have seen this problem as well.

Rapidly connecting and disconnecting can cause strange errors.  I thought
it might be something to do with the garbage colection in .NET >>

Does this happen in a normal C# application ?  If so, can you send me an
example that reproduces it ?  I know that you pasted a sample in the last
message, but the ".. do something here" part could make a big difference in
what happens.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Jun 5 2007 3:11 AMPermanent Link

Chris Holland

SEC Solutions Ltd.

Avatar

Team Elevate Team Elevate

Hi Tim,

It is not easy to repoduce.
It never happens in a consistent time or place.

When I have had it happen the "..do something here" code was importing
and converting large amounts of data, so it could have been something in
there screwing the memory, but as soon as I took the connect and placed
it outside the loop all worked fine.


Chris Holland
SEC Solutions Ltd.

Tim Young [Elevate Software] wrote:
> Chris,
>
> << I have seen this problem as well.
>
>  Rapidly connecting and disconnecting can cause strange errors.  I thought
> it might be something to do with the garbage colection in .NET >>
>
> Does this happen in a normal C# application ?  If so, can you send me an
> example that reproduces it ?  I know that you pasted a sample in the last
> message, but the ".. do something here" part could make a big difference in
> what happens.
>
Tue, Jun 5 2007 1:33 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Chris,

<< It is not easy to repoduce.
It never happens in a consistent time or place. >>

Wow, even with just straight C# code it does this ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Page 1 of 3Next Page »
Jump to Page:  1 2 3
Image