Link to home
Start Free TrialLog in
Avatar of Dominic34
Dominic34Flag for Canada

asked on

Lost connectivity with database from PocketPC

Hi,

We have an SmartDevice application, build in VB.net 2005 to manage inventory in a huge warehouse. The software connect to a SQL Server 2000 database upon entering any program's functionnality. But after a few minutes of idle, the database connection drop by itself, even if the PocketPC does not fall in sleep mode. So the operator have to get out of the current menu and re-enter it (the database connection is re-established in the form's Load method).

Any idea why the database connection drop like that? How can I fix this?

thanks for your time and help
Avatar of kdwood
kdwood

Dominic,

Can you provide the following details:

1.  What type of Smart Devices are you using?
2.  Are your Smart Devices wireless?
3.  Are you connecting to an SQL 2000 server?  If so, what method are you using to connect?

Regards,

Keith
Avatar of Dominic34

ASKER

1. Those are Teklogix Workabout Pro G3 and Symbol MC9090 running Windows Mobile 5.0
2. Yes, wireless
3. yes, SQL 2000. using SQLClient.SQLConnection method:

oCnn = New SqlClient.SqlConnection
            With oCnn
                .ConnectionString = "Server=" & ServerName & ";Database=" & DBName & ";" & _
                                    "User ID=" & UserName & ";Password=" & Password & ";" & _
                                    "Trusted_Connection =" & Trusted
                .Open()
            End With
ASKER CERTIFIED SOLUTION
Avatar of kdwood
kdwood

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
1. Hibernate isn't enabled Nor is sleep mode.
2. It's an old application that run very well on other warehouses. This particular warehouse is new, PocketPC are new also
3. AP are configured exactly like the AP's at the other warehouses
4. That's a thing I was considering also, to modify the application to reconnect each time at the database on every StoredProc calls... would be a bit time consuming to do, but would fix the problem I guess...