Page 1 of 1
Error "revdberr,invalid database type"
Posted: Mon Jun 13, 2011 3:30 pm
by akshu
I am running LiveCode on a Windows XP and when I run my code on here, it works fine with no errors. However, when I test it out on an Android I am getting the error "revdberr,invalid database type".
Code: Select all
put revOpenDatabase("ODBC", tDatabaseAddress, tDatabaseName, "", "") into tResult
How do I get past this error? Any help would be appreciated.
Thanks.
Re: Error "revdberr,invalid database type"
Posted: Mon Jun 13, 2011 4:35 pm
by Klaus
Hi akshu,
ODBC database access is not (yet) supported on LiveCode Android!
Please check the "Android Release Notes" (LiveCode: Menu: Help)
to see whats currently supported and whats not.
Best
Klaus
Re: Error "revdberr,invalid database type"
Posted: Mon Jun 13, 2011 8:38 pm
by akshu
Hi Klaus,
Thank you for the quick response. Do you know if/when it will be supported?
If I am trying to connect to SQL Server, is there something else I can use, other than ODBC?
Thank you.
Re: Error "revdberr,invalid database type"
Posted: Tue Jun 14, 2011 2:10 pm
by Klaus
Hi akshu,
only SQLite and MySQL database access is currently supported on Android.
I may repeat myself but:
Please check the "Android Release Notes" (LiveCode: Menu: Help)
to see whats currently supported and whats not.
Best
Klaus
Re: Error "revdberr,invalid database type"
Posted: Tue Jun 14, 2011 8:18 pm
by Janschenkel
Even with generic ODBC support, you'd still need a specific Android-compatible driver for the back-end database.
There is definite value in an SQLite driver on mobile platforms, but those mobile apps shouldn't connect to remote databases on a server directly. Remember that for most commercial database management systems, you pay per connection. Mobile apps may not be using these connections in an optimal way, as their network may drop, or the user may switch to another app, etc.
A better architecture (also from a security point of view) is to expose your business logic as HTTP(S) web services. This avoids version problems as well (think of an outdated version of the mobile app, unaware of database schema changes until it is updated to a more recent version. With a clear API for remote applications, be they mobile or desktop apps, you have a solid, scalable n-tier solution within reach.
Such n-tier applications can be built with LiveCode - both the front-end and the back-end. And with technology-agonistic web services, you can built your web services using .NET or Java, if a LiveCode Server solution isn't achievable.
Jan Schenkel.