Hi, I'm having a problem with generated code for CF2.0. When I run generated VS2005 project I have (as a default setting) used SQLCeConnection to connect to SQL Server. It is obvious but this is not what I need.

I would like to connect using Compact Framework 2.0 to SQL Express 2005. SQLCeConnection class doesn't support this connection ( it can only connect directly to *.sdf file ) What can I do to generate code under Compact Framework 2.0 with is connecting using SQLClient from System.Data namespace(this class enables connections to SQL Server 2005 database ) instead of using SQLCeConnection ??

I would be thankful for any answer.

You mean make a remote connection to a sqlserver db from the handheld/smart device? That's not supported. You should connect to a local SqlCE db.

I understand, do you want to support this functionality in the near future ?

( I think, that this is not a big problem to change one class from SQLCeConnection to SQLClient class , but meaby I'm wrong...)

I really need this for my Company...

m.gren wrote:

I understand, do you want to support this functionality in the near future ?

No, we probably won't make this change. The problem is mainly about security. If any roaming wireless device is able to connect to your sqlserver database, you don't really have control over what will happen next.

This is true but if you are using VPN network, not wireless, and you have a computer with Windows CE 5.0 as a ThinClient - InfoKiosk - this solution will work and we don't have to worry about security becouse this is Industrial Network , only for ThinClients...

well, I will have to search for other solution...

Otis wrote:

No, we probably won't make this change. The problem is mainly about security. If any roaming wireless device is able to connect to your sqlserver database, you don't really have control over what will happen next.

If I may add my 2c here: it don't see your argument (the security risk) as a reason for not to provide this support (mobile <-> SQL Server 2000/2005).

I mean, can security be a reason whether or not to support something, in this discussion I mean. Because one can develop alot of other security risks in the other supported scenarios. I can imagine a laptop in the same situation as a pda could be (in the field, using wifi or GPRS). So where's the security there?

khelb wrote:

Otis wrote:

No, we probably won't make this change. The problem is mainly about security. If any roaming wireless device is able to connect to your sqlserver database, you don't really have control over what will happen next.

If I may add my 2c here: it don't see your argument (the security risk) as a reason for not to provide this support (mobile <-> SQL Server 2000/2005).

I mean, can security be a reason whether or not to support something, in this discussion I mean. Because one can develop alot of other security risks in the other supported scenarios. I can imagine a laptop in the same situation as a pda could be (in the field, using wifi or GPRS). So where's the security there?

The security argument is mainly the reason why not a lot of people will use the setup discussed here. Suporting the compact framework is already a big pain due to lack of serious testing abilities (that seems to change in orcas I believe) and limitations of the compact framework, and if we now also have to provide two DQE's, testing will be an even bigger problem, and if I then look at the potential group of people using this, I think the group is very small, especially because sqlservers most of the time aren't made available for everyone to access: most usages of the compact framework here is either: - a thin client solution so you access a webpage for example or a webservice or - a local CE database so you don't have to access any central db.