Re: Oracle as Front End for Ms Access

From: Mark D Powell <>
Date: Wed, 27 Feb 2008 06:51:41 -0800 (PST)
Message-ID: <>

On Feb 27, 5:01 am, SePp <> wrote:
> Hello all,
> I'm looking for the pro's and con's for an MS Access Application which
> has an Oracle backend (Oracle Express).
> Especially how it is about the auto commit ( I believe it is off ),
> the multi user security and the speed of the application.
> I know Oracle is very good with multi users but how is it when I
> use MS Access as Frontend.
> Is it still good, with the ODBC Connection and the linked tables?
> What is about the ODBC connection. This slows the queries extremely
> down, doesn't it?
> Very much thanks in advance!
> Kind regards,
> SePp

Lots of places use Access as a front-end application with Oracle on the backend. As long as the application designers understand how Access works via ODBC then low load applications generally work fine. Many of the issues in relation for Oracle being the back end store also exist when SQL Server is the back end store. Access will automatically lock rows in certain situations and you need the application to release them in a timely fashion.

HTH -- Mark D Powell -- Received on Wed Feb 27 2008 - 08:51:41 CST

Original text of this message