Re: SQL Worksheet changes not seen via ODBC?

Not a dumb question. I can bet that's the case. Since create drop commands automatically issue a commit .. that is what's happening.

He needs to issue a commit ..i.e. he needs to type "commit;" after those update/insert/delete statements.

.. and a reading of Oracle Concepts Manual is required.

Anurag

"Michael Segulja" <msegulja_at_yahoo.com> wrote in message news:pan.2002.08.27.10.27.12.605032.28029_at_yahoo.com...
> On Tue, 27 Aug 2002 09:07:09 -0500, David Mueller wrote:
>
> > When I update/insert/delete data from tables using the SQL Worksheet
> > (v1.3.6) I cannot see those changes via my Access 97 ODBC link - unless
> > I change the structure of an index, or delete/add an index, of the
> > tables involved.
> >
> > Facts:
> > 1. Different ODBC drivers work.
> >
> > 2. When Access changes data - even local instances on different
> > workstations - the changes can be seen immediately at any/all ODBC
> > connections and from the SQL Worksheet.
> >
> > Any ideas why changes via the SQL Worksheet cannot be seen in Access97?
> > Thanks,
> > David
>
>
>
> This may be a really dumb question, but after the changes you make in SQL
> Worksheet, do you issue a commit? You didn't mention that you did, but
> that's the first thing that pops into my mind.
>
>
>
> Michael
Received on Wed Aug 28 2002 - 03:32:44 CEST