How Oledb connection should be Declared

[Manesh Pawar]

Hello
I m new in asp.net c#.
How to declare a oledbconnection object in asp.net c#.
Means should it be declared as a static or public?
ex:- suppose the object is
OleDbConnection con;
Whether it should be
static OleDbConnection con;
Or
public OleDbConnection con;

[Frinavale]

The Public scope modifier indicates that the variable is accessible other code. This means that other code can access and use the variable.

The Static modifier indicates that this variable is static/shared amongst all instances of the class. So if you have instantiated 4 instances of the ABC class (you have 4 ABC objects)...all 4 objects will share the same variable.

Be very careful about sharing connections between classes! You could experience problems while opening/closing the connection if another class is using the same connection.

-Frinny

[mzmishra]

static keyword allows you to make a variable/object/method be "shared" across all instances of a given object.
A public is an access modifier which means that it is the scope of this construct is public i.e. anyone can use it.

You can read this article to get different Variable and Method Scope in Microsoft .NET
http://msdn.microsoft.com/en-us/library/ms973875.aspx

[Manesh Pawar]

Hello Sir,

Thanx
Actualy i hav a single database connection used in application, And I m facing the same problem of Opening/ Closing Connection. But It occurs sometimes, and sometimes it Works.
I am using "static OledbConnection con;" and it is being used in all functions

What should I do To fix that problem? and When Should I open/ Close Connection?

[Frinavale]

You should only open a connection when it is needed and after you have finished with it you should close it.

The problem with using a static connection is that some objects are going to try opening and closing the connection while others are using it.

I strongly recommend against this approach...unless you want to take the time to implement a solution that works around the problem...but you'll probably run into other problems along the way.

This will become a bigger problem as your site becomes more active.


-Frinny

[Manesh Pawar]

Yes Sir, I will Fit it into my mind.

I am Using MS-access. Is There Any Problem With MS-Access database in case of concurrency?

[NeoPa]

Access databases can handle concurrency. My only experience of controlling this is within the options of the Application though.

It is generally considered that it doesn't handle many concurrent connections well though. Access as a back-end for web based applications should probably only be used sparingly and in circumstances where you know it to work and know that the usage will never grow beyond what Access can handle well.

[Manesh Pawar]

Ok Thank you, Sir