Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Problems with Oracle as backend and Access 2000 as frontend
- Thread starter cecily
- Start date
The only issue is performance, going through an ODBC will decrease performance. If your database is only going to be accessed trough access, you should look at SQL server which is much cheaper. Too bad I.T. is not cash business
Luc Foata
Unix sysadmin, Oracle DBA
Luc Foata
Unix sysadmin, Oracle DBA
Problems (just what I've learned to date in the same quest...):
-Access SQL is closer to ANSI 92 and, of course, VBA functions are not supported by Oracle. Vice versa, the oracle functions are not usable in Access
-Access doesn't have a PL/SQL engine, so you can't do this client side
-ODBC is slow, and effective ADO use will require writing the code for unbound forms
-Limitations & bugs of ADO & Providers
-Access SQL is closer to ANSI 92 and, of course, VBA functions are not supported by Oracle. Vice versa, the oracle functions are not usable in Access
-Access doesn't have a PL/SQL engine, so you can't do this client side
-ODBC is slow, and effective ADO use will require writing the code for unbound forms
-Limitations & bugs of ADO & Providers
- Status
Similar threads
