Windows Mobile 5 - C# - SQL

[GeordieLife]

Hi

I'm a programmer of some 8 years now. Currently doing a lot of C# desktop style applications with SQL Server back end. Moving onto manufacturing systems (which I've previously developed in VB6/C#).

Right, been tasked with pulling together an application for a Windows Mobile 5 device (10 of them or so).

Needs to be able to communicate directly with SQL Server 2000/2005.

Is there any way of doing this?

What's the best way of doing this?

Many thanks in advance!

 

[Markbnj]

Depends on the environment. Are the devices going to be used across public wifi networks, or just within the building? Techniques I have seen used in the past include store-and-forward, and webservices.

 

[GeordieLife]

On site. Barcode scanning: booking in/out, moving stock etc. Needs to be able to interract with the ERP/MRP system real time to check for orders and stock.

Thinking of web services or maybe investigating WPF. Ideally i'd have just done a C# application and connected directly to SQL but having no luck.

 

[Atheus]

Originally posted by: Markbnj
webservices.

This would be my first thought - SOAP web services. If you can't connect directly that is. What happens when you try?

 

[Markbnj]

Originally posted by: GeordieLife
On site. Barcode scanning: booking in/out, moving stock etc. Needs to be able to interract with the ERP/MRP system real time to check for orders and stock.

Thinking of web services or maybe investigating WPF. Ideally i'd have just done a C# application and connected directly to SQL but having no luck.

WPF is just a presentation layer technology. You might have been thinking of WCF. In any case, you probably can't connect directly to the database due to port restrictions somewhere in the network link. Is this straight-up 802.11? I'd look at firewall settings on the device and access point.

But connecting right to the database probably isn't the best approach. Any mobile application needs to account for the times when connectivity is lost.

 

[imported_Dhaval00]

In addition to what Mark said, also be wary that Web Services deal in XML - meaning, the traffic flowing back and forth is verbose. If you use WCF, stick to RPC calls unless interoperability is an issue.

 

[KLin]

http://msdn.microsoft.com/en-u.../aa275613(SQL.80).aspx

You can have a c# app running on a mobile device connecting directly to a SQL server. The company I work for has done this for several clients.

It's just a c# app designed with the compact framework accessing a SQL server over wifi. It of course uses the data provider in the link above to make the connection.

 

[JasonCoder]

Couple things...

When you say "communicate directly" with the SQL Server, I'd assume you have wifi EVERYWHERE the device is going? Get ready for lots of support for users leaving the wifi range. If that's not EVER going to happen then party on the data directly like what KLin posted. However if that's not the case then you may want to look at smart client dev. One example is that the user works on local data caches and then syncs up with a SQL Server. The stuff that ms has put out (even in just the last 6 months) around sync is amazing.

 

[GeordieLife]

Hi

Thanks for your responses. The guns will be used in an area with 100% wifi coverage.

It needs to check with SQL with every user interaction so syncing is out. It has to be real time unfortunately.

I'll have a look at that link when I get chance.

Stew