SQLAnywhere webservices on Windows Mobile without a network

[justin_willey]

Newbie Alert - we are just starting to experiment with SQLA on Windows Mobile so may be missing deeply obvious things!

Environment:

• Windows Mobile 6.1 professional
• CE OS 5.2.20776 (Build 20776.1.4.9)
• SQL Anywhere 11.0.0.1.1490
• device: Datalogic Memor

The general idea is a very simple cross-platform mobile application, interacting with data synchronised periodically with the server using Mobilink. To get round all the cross-platform issues, we want a have web application, and hope to use the SQLAnywhere web server to deliver it. This would give us an easily deployable application and data synchronisation solution in one go - everything would be in the database.

The mobile devices will be being used in situations where there is usually / often no wireless (or wired) connectivity (if it was always available we wouldn't need data synchronisation of course!).

SQLA installs fine, database starts fine. A trivial prototype application works fine when the mobile device has a WiFi connection, Internet Explorer opening the webservice "page" at 127.0.0.1. However when there is no WiFi connection, IE reports "Action cancelled. IE cannot link to the page requested...." A dialogue box also comes up saying "cannot connect with current connection settings"

My question is: why cannot the local SQLAnywhere webservice be seen, just because there is no Wifi connection, and is there a way around this?

[Former Member]

Justin,

This seems like a configuration issue on your device. The web service should be picked up by Pocket IE whether or not you have WiFi connection. I did a quick Google search for the error "cannot connect with current connection settings" and got hits about changing your configuration, particularly around ActiveSync (try Programs > ActiveSync and close it. Don't know why that would matter).

I think the problem is that Pocket IE wants to use a particular connection for all its HTTP traffic and fails because it cannot find it.

Hopefully this helps you out.

José

[justin_willey]

Thanks for taking a look at this José. As you say, IE is getting upset. Doing some more reading around, I think it maybe that IE is looking for a DNS server as a matter of course (even though it doesn't need one in this case) and getting upset because it can't find one. Active Sync isn't involved (or running) in this case. Mmmm...