I am not familar with the concept, but will investigate.
-------------- Original message --------------
> In Oracle a view can be given an "instead of" trigger which essentially
> is the work-around for doing updates through a non-updateable view.
>
> Any such thing in Pervasive?
>
> Bob
>
> [EMAIL PROTECTED] wrote:
>
> > Excellent idea, however Pervasive does not allow updates through a
> > view, even a single table view. This application has to update the
> > values in the column. I thought about using SSQL for the update, but
> > I am needing to use an ON AFTER INSERT TRIGGER and SSQL is not
> > supported in stored procedures nor in EEP's.
> >
> > Thanks for the suggestion and if I was just needing to retrieve the
> > data, it would have worked.
> >
> > -Bob
> >
> >
> > -------------- Original message --------------
> >
> > > Is it at all possible to get into the Pervasive database and
> > create a
> > > view on top of the table?
> > >
> > > This would allow you to alias the column names (assuming
> > Pervasive is
> > > similar to Oracle) so that R:Base has absolutely no idea of the bad
> > > column name.
> > >
> > > As long as this is a new view you wouldn't be impacting the
> > third-party
> > > package that you are attempting to extract data from.
> > >
> > > Bob
> > >
> > > [EMAIL PROTECTED] wrote:
> > >
> > > > Gunnar,
> > > > Thank you for the reply. Indeed, I do connect to this very same
> > > > table on a daily basis and make both queries and updates without
> > > > any problems. It is not just this one column named REFERENCE.
> > > >
> > > > As mentioned, either with ANSI on or off, I cannot get to the
> > data
> > > > or update it. The database is Pervasive and is used by AccPac
> > > > accounting software. I have several fairly complex
> > applications that
> > > > are integrated with AccPac / Pervasive and they work quite
> > well, both
> > > > updating and retrieving data.
> > > > This column is proving to be a problem though.
> > > >
> > > > Does any one know if this might be an issue to submit as a fix or
> > > > would it be related more to the Pervasive ODBC driver not doing
> > > > something correctly?
> > > >
> > > > Thanks,
> > > > -Bob
> > > >
> > > >
> > > > -------------- Original message --------------
> > > >
> > > > Bob
> > > >
> > > > I was involved in this issue a while back. I my case it was
> > ACCESS
> > > > DB with field name that broke the naming convention.
> > > >
> > > > When I first tried with alias name I was happy for reading, but I
> > > > could use SSQL UPDATE. In my case it was solve by SET ANSI OFF as
> > > > you suggest. Then in my cas both select update declare cursor or
> > > > whatever works. (Sometimes with not so good speed since as far as
> > > > I understand I have only on one primary key in the ODBC table.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > If SET ANSI off does not help you, what is your Foregin DB, have
> > > > you tried an other table without a reserved word, if that works
> > > > maybe there is an issue for setting. ODBC seems to be very
> > > > specific for certain settings.
> > > >
> > > >
> > > >
> > > > Gunnar Ekblad
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > *From:* [email protected] [mailto:[EMAIL PROTECTED] *On Behalf Of
> > > > [EMAIL PROTECTED]
> > > > *Sent:* den 16 mars 2005 15:39
> > > > *To:* RBG7-L Mailing List
> > > > *Subject:* [RBG7-L] - Invalid Column Name & ODBC
> > > >
> > > >
> > > >
> > > > I have a foreign database that I must connect to via ODBC. This
> > > > database has a
