C# SqlClient or C# OLE Access

[Jason Huang]

Hi,

In our old Aplication, we used to have MSAccess MDB in every client's PC,
The AP calls the MDB, then by ODBC connection the MDB will call the SQL
Server.
We have this way for years.
But now we are thinking if our new Application sould apply that approach,
or we have our new AP to connect to the SQL Server directly.
Given that our environment is ASPNet C# and SQL Server 2000 in Windows
Server 2003.
Which way will be more secure?
Any help will be appreciated.

Jason

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

Connect directly to SQL server, the performance otherwise will suffer.

And frankly I do not see how the otherway will help with the security.


cheers,

 

[Miha Markic [MVP C#]]

Hi Jason,

I agree with Ignacio. Go with SqlClient - it is faster and has more
features.
What do you mean by secure?

 

[Michael S]

Hi,

In our old Aplication, we used to have MSAccess MDB in every client's PC,
The AP calls the MDB, then by ODBC connection the MDB will call the SQL
Server.
We have this way for years.
But now we are thinking if our new Application sould apply that approach,
or we have our new AP to connect to the SQL Server directly.
Given that our environment is ASPNet C# and SQL Server 2000 in Windows
Server 2003.
Which way will be more secure?
Any help will be appreciated.

Jason

If you want security, just pull the plug. 100% security guaranteed.

Your actual question should be a no brainer. The System.Data.SqlClient
namespace is (more or less) built for Microsoft SQL Server. Is this really a
topic at your company? I'm picturing your manager as Tweek from South Park
going - AAh, All these questions about connectivity is making me nuts. Aaah!
*tweek*

Have a cup of coffee and relax.

Happy Coffee
- Michael S

 

[Jason Huang]

Thanks Miha.
In our old Application(VB6 coding), it uses a UserList in the SQL 6.5 to
decide who has privilege to access some particular form, e.g., the
accountant can access the Accounting Form, but not Personnel Form; the
personnel can access the Personnel Form, but not Accounting Form.
Each client has to has it's MSAccess mdb in order to connect to the SQL 6.5,
via building the ODBC by a SQL user account.
We have the system goes for couples years.
But we are thinking if we can improve our New Application in security,
accessibility and stability, given that in the ASPNet C# environment.

Hi Jason,

I agree with Ignacio. Go with SqlClient - it is faster and has more
features.
What do you mean by secure?

--
Miha Markic [MVP C#]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

Hi,

In our old Aplication, we used to have MSAccess MDB in every client's PC,
The AP calls the MDB, then by ODBC connection the MDB will call the SQL
Server.
We have this way for years.
But now we are thinking if our new Application sould apply that approach,
or we have our new AP to connect to the SQL Server directly.
Given that our environment is ASPNet C# and SQL Server 2000 in Windows
Server 2003.
Which way will be more secure?
Any help will be appreciated.

Jason