Re: MS Access & Oracle
Date: 1997/08/18
Message-ID: <33f9ed5e.824858_at_news.nuernberg.odn.de>#1/1
i did development in access since early 1993.
there are some troubles with ms-access:
- if you use dynasets (that goes through MS-Jet) on ODBC access
creates a "virtual" unique key for every data tupel in the query.
based on that access updates the underlying tables. This process leads
to a lot of sql send to oracle.
- one workaround is to use passthrough queries - but access won't be
able to update those !
- updating tables works only if there is at least one unique index for
them. to identify rows access uses the FIRST UNIQUE INDEX FOUND in the
oracle dictionary
ways to come around the limitations:
1. use another windows dev environment with bypass to odbc my personal
choice is borland's delphi - excellent architecture, true compiler
fantastic performance
2. use visual basic with RDO (remote data objects)
3. use developer 2000 (i suggest you use designer 2000 as well then)
yours
On 13 Aug 1997 09:30:17 GMT, "José Miquel" <pmiquel_at_drac.medusa.es> wrote:
>I have change an application that was developed over MS Access and the data
>was managed by MS Access.
>Now, the data has been exported to Oracle 7.3, and via ODBC the application
>in MS Access is reading and updating the data.
>The result is that the speed of the application has not increased, in some
>times the speed has decreased.
>I think that the problem is possible will be in the application MS Access
>that has not been develped thinking in a RDB engine like Oracle.
>If somebody have an answer for me, i will be congratulated
>My name is Pepe, from Spain
>My E-mail: pmiquel_at_drac.medusa.es
>Thank you
Christian Kaas
Client/Server development and consulting
Fax. 49-9129-5518
Phone 49-9129-5508
Received on Mon Aug 18 1997 - 00:00:00 CEST