Access
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller
Re: Access
Does 'transfer that information in' mean move it to another database?
Theoretically, you could put it into something else (SQLite, for instance), and connect to it in Access via ODBC, provided you have the proper ODBC driver for the new database engine.
Theoretically, you could put it into something else (SQLite, for instance), and connect to it in Access via ODBC, provided you have the proper ODBC driver for the new database engine.
-
Steve Denney
- Posts: 101
- Joined: Wed Dec 22, 2010 8:17 pm
Re: Access
Hi, Access is an odbc database.
You can construct SQL statements in your livecode app and have them executed by Access. Livecode's database library also includes a number of useful commands & functions (all starting with revdb).
So...
Transfer that information in? Definitely, you can import your Access database into your app and display it in any fashion you choose. You can update, edit, delete, sort, search (and more) your database. This goes both ways, meaning you can change the data in Access too.
Keep the functionality of forms and reports? Not sure. Presumably you could write SQL to duplicate said forms/reports, but that’s hardly keeping them.
Steve
You can construct SQL statements in your livecode app and have them executed by Access. Livecode's database library also includes a number of useful commands & functions (all starting with revdb).
So...
Transfer that information in? Definitely, you can import your Access database into your app and display it in any fashion you choose. You can update, edit, delete, sort, search (and more) your database. This goes both ways, meaning you can change the data in Access too.
Keep the functionality of forms and reports? Not sure. Presumably you could write SQL to duplicate said forms/reports, but that’s hardly keeping them.
Steve