Please do not crosspost; you already posted this question in the Android forum.

You can treat them as ODBC data sources and should be able to sync against them that way. I know this works for Oracle at any rate, providing you have the Oracle client installed on the machine that will provide the data source.

Thanks A Lot, Dude @Richard_MacCutchan

Ok guys - I guess the verdict's in. It's what I thought initially thought would be the case too. Its just that the doco on Correlated vs Uncorrelated sub-queries threw me a little, where correlated sub-queries are re-evaluated for each row of the main query. I do agree, however, that re-evaluating the sub-query will be significantly better than searching the full result set. Cheers people.

Thank you very much, John. I will see and try ...

How about something like: Cursor res = dataHelper.getAllData(position); ... public Cursor getAllData(int position) { SQLiteDatabase db = getReadableDatabase(); Cursor res=db.rawQuery("select * from "+Table_Pro+" where id="+position,null); return res; } But that seems rathger silly when the data has already been retrieved into listpro. Why not: String s = listpro.get(position); Of course you'd have to modify getAllProvinces() to store more than just an array of String types. "One man's wage rise is another man's price increase." - Harold Wilson "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons "You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles

Like this guy?[^] On a side note, the game that is from is AWESOME. What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???

In your ChinookContext class, remove the line you have in the OnModelCreating method. You don't need it. Also, your DbSet lines are bad. They should be: public DbSet Artists { get; set; } public DbSet Albums { get; set; } I HIGHLY suggest you don't take all of your information on EF from "some tutorial on the web" because you're missing a SHIT TON of information that these tutorials are not tell you. Pick up this book[^]. It's an older book, covering EF4, but it's better than the newer books out there that were released last year. A guide to posting questions on CodeProject Click this: Asking questions is a skill. Seriously, do it. Dave Kreskowiak

It is quite a simple matter to display the full text of your query to see exactly what values it contains.

Thank you bro u solved the problem tnx again

And what will happen if they do not? You should never create an application that assumes your users will have some software package installed.

intelstar venus wrote: The problem was in using bad logger function. In general that should never happen. A good logger should not normally impact an application if the logger fails.

A step-by-step guide: 1. Download the SQLite drivers (zip file). Expand the zip somewhere locally and note the location. 2. Put the sqlite_jni.dll from the zip into your JRE's bin directory. 3. In Eclipse with DTP 1.0 installed (preferably the final build or a nightly build dated 110806 or later), go to the Preferences (Window->Preferences) and select the Connectivity->Driver Definitions page. 4. Select the "Generic JDBC" category in the Available Driver Definitions tree and click "Add...". 5. Select "Generic JDBC Driver->Generic JDBC Driver" in the Available Driver Templates tree. Give the new generic JDBC driver a name like "javasqlite JDBC driver". Click OK. 6. Click "Add Jar/Zip" and select the sqlite.jar from the driver zip you expanded in step 1. Click Open. 7. In the Properties table, select the Driver Class property and click the "..." button. If the jar is accessible, you will see a dialog appear with at lease one class in the list. Select "SQLite.JDBCDriver". Click OK. 8. Also in the Properties table, select the Driver URL property and type the following: jdbc:sqlite:/DRIVE:/dirA/dirB/dbfile. 9. Click OK on the Edit Driver Definition dialog. You should see your new driver appear in the driver list on the Driver Definitions preference page. 10. Click OK to close the Preferences dialog. 11. If the Data Source Explorer is not open, open the Connectivity->Data Source Explorer view from the Window->Show View menu or open the Database Development perspective from the Window->Open Perspective. 12. In the Data Source Explorer, right-click on the Databases category and select New. 13. In the New Connection Profile wizard's Wizard Selection Page, choose the SQL Model-JDBC Connection entry in the list and click Next. 14. Give your new profile a name like "SQLiteTestDB". Click Next. 15. In the "Select a driver from the drop-down" combo box, select your new SQLite driver definition. Modify the file path in the sample URL to match the path to your local SQLite database. 16. Click "Test Connection" to verify you can connect to your database. 17. Click Finish to create the profile. 18. In the Data Source Explorer, right-click on the new profile and select Connect. You should see content appear in the tree beneath the profile. Browse through your database to view available tables and their columns. You also read more about the best practice of mobile app development on Android from Iflexion company.

If it's using AGPL v3 then you can publish under GPLv3. cheers Chris Maunder

USE SQLITE database and store your server database data in Android local SQLite database. Learn Android development. https://itinsidenews.com

Been there done that, but in WCF. In design time you're apparently not using the app.config you think you are. There's a description and kind of solution to one of the ways this problem can occur here[^]. Wrong is evil and must be defeated. - Jeff Ello

return ourdatabase.insert(DATABASE_NAME,null,cv); That is the name of your database, not the table it contains.

I was under the impression you could only have 1 datareader active at any one time, I assume EF spit uses datareader as the underlying connection type. The second connection may be being reject on that basis. Never underestimate the power of human stupidity RAH

OK. Or C# can call a C++ DLL with P/Invoke?