Connect to a SQL Database

by AntoniMG » Wed, 08 Jul 2009 01:02:43 GMT


Sponsored Links
 Hi,

Im triying to connect to a SQL Database with Android, this is my code:

package com.example.conversor;
import java.sql.*;

import android.app.Activity;
import android.os.Bundle;
import android.view.View;
import android.widget.Button;
import android.widget.EditText;

[...]

try {
Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
} catch (Exception e) {
e.printStackTrace();
}


try {
DBConnSQL = DriverManager.getConnection("jdbc:sqlserver://zeus:
1433;DatabaseName=dsnew;","sa","sapass");
} catch (Exception e)
{
e.printStackTrace();
}

And this is what i get:

07-07 11:16:27.450: ERROR/jdwp(1597): Failed sending reply to
debugger: Broken pipe
07-07 11:16:29.832: ERROR/dalvikvm(1605): Could not find class
'javax.sql.XAConnection', referenced from method
com.microsoft.sqlserver.jdbc.SQLServerConnection.close
07-07 11:16:29.931: ERROR/AndroidRuntime(1605): Uncaught handler:
thread main exiting due to uncaught exception
07-07 11:16:29.983: ERROR/AndroidRuntime(1605): java.lang.VerifyError:
com.microsoft.sqlserver.jdbc.SQLServerConnection
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
java.sql.DriverManager.getConnection(DriverManager.java:192)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
java.sql.DriverManager.getConnection(DriverManager.java:228)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
com.example.conversor.ConversorAct.onCreate(ConversorAct.java:39)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:
1123)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:
2231)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:
2284)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
android.app.ActivityThread.access$1800(ActivityThread.java:112)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:1692)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
android.os.Handler.dispatchMessage(Handler.java:99)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
android.os.Looper.loop(Looper.java:123)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
android.app.ActivityThread.main(ActivityThread.java:3948)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
java.lang.reflect.Method.invokeNative(Native Method)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
java.lang.reflect.Method.invoke(Method.java:521)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run
(ZygoteInit.java:782)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540)
07-07 11:16:29.983: ERROR/AndroidRuntime(1605):     at
dalvik.system.NativeStart.main(Native Method)



SQL Server is correctly installaed and configured, and receiving
Querys from other app.

Thanks.




--~--~---------~--~----~------------~-------~--~----~



Connect to a SQL Database

by Charlie Collins » Wed, 08 Jul 2009 04:06:08 GMT


 n general you don't want to do that - connect directly to your SQL
server from Android. If your Android device is on the same subnet,
and you configure host resolution and port access, you *might* be able
to do that, I have never really thought to try, but it's certainly not
the normal path.

Normally, you will want a server side API, like REST or such, that you
can call from Android using HTTP or something. That way your device
can connect to your server side API and it doesn't need to know
anything about it being a SQLServer (the abstraction is at a different
level), and it will work regardless of whether or not you are on the
same subnet. Have a look at a REST implementation for your favorite
server side language (Jersey for Java, whatever for .net, etc) and
create a simple server side for your Android app to connect to, and
try that.

On Jul 7, 7:18am, AntoniMG <tonio...@gmail.com> wrote:
--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. Its a Zoooooommmm MDK (ZoomMDK)

Hey guys,

maybe I've got something interesting for you ;D

"Someone" sent me a ZoomMDK as a present (doesn't want to be named),
which is a generic Hardware platform, which is officially able to run
Android. TI is the big one behind. Tomorrow I'll get it from my local
customs and start reviewing it and document my experiences.

All that will be posted on anddev.org. First article of many:
http://www.anddev.org/part_0_-_what_is_the_zoom_mdk-t1968.html

If I got it running, my plan is to test hardware-intensive appliations
(like Tom Gibaras MoseyCode, Andnav, and maybe YOUR app) on this real
device. Then we will see how well performing the device is against the
emulator.

Stay tuned :)

Regards, plusminus
http://anddev.org
#  Worlds largest Android Development Community / Tutorials

(sorry for posting in multiple forums)
--~--~---------~--~----~------------~-------~--~----~

2. Run two android instances on the same host and comunicate betwen them using socket

Hi everybody,

I'm new at Android, so please be patient if my questions are too
simple.
I would like to run two (or more) android instances of the emulator on
the same host (windows vista),
and comunicate between them using Sockets.

Can anybody describe in detail, the passes i should take.
Please be patient, and give the more information you can.
Any piece of code would be appreciated.

Thanks everybody,

Oskeol

--~--~---------~--~----~------------~-------~--~----~

3. Looking for a fast UI platform for embedded linux

4. thunderbird client issues

5. OSCAR/XMPP/IRC chat client

6. chat client

7. Compiling and Installing Androin in Pocket PC