Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 7CFC6B5D8BD for ; Mon, 23 May 2011 15:01:24 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 02275-04 for ; Mon, 23 May 2011 18:01:17 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-pv0-f174.google.com (mail-pv0-f174.google.com [74.125.83.174]) by mail.postgresql.org (Postfix) with ESMTP id 462AFB5DBD2 for ; Mon, 23 May 2011 15:01:16 -0300 (ADT) Received: by pvg12 with SMTP id 12so2658132pvg.19 for ; Mon, 23 May 2011 11:01:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.32.226 with SMTP id m2mr2432946pbi.444.1306173676280; Mon, 23 May 2011 11:01:16 -0700 (PDT) Received: by 10.68.41.161 with HTTP; Mon, 23 May 2011 11:01:16 -0700 (PDT) X-Originating-IP: [66.215.95.51] In-Reply-To: <201105231853.47726.projserve@gmail.com> References: <201105231853.47726.projserve@gmail.com> Date: Mon, 23 May 2011 11:01:16 -0700 Message-ID: Subject: Re: problem with update data sets from front ends 8.4, Ubuntu 10.04 From: Samuel Gendler To: Dean le Roux Cc: pgsql-sql@postgresql.org Content-Type: multipart/alternative; boundary=bcaec51ddbe5fd5bd204a3f54135 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-5 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201105/136 X-Sequence-Number: 35420 --bcaec51ddbe5fd5bd204a3f54135 Content-Type: text/plain; charset=ISO-8859-1 On Mon, May 23, 2011 at 9:53 AM, Dean le Roux wrote: > postgres 8.3 to 8.4 Open office base 3.2 Ubuntu 9.04 to 10.04 (new > install) > > I recently upgraded from Ubuntu 9.04 to Ubuntu 10.04. Security and other > updates have been effected. I used webmin to restore the databases. > > Since migrating to Linux around 2006 we were successful in converting our > mdb > file to postgresql - only one glitch was a difference in -1 as YES. We > successfully used the systems with open office as a front end for the last > few > years. Until now - after the upgrade I can view data but not update data. > > Experience with sql is very limited as I have always used sql query > builders > over the years. The system has worked well with multiple tables, and in the > past there was no problems with sending sql statements to postgresql. > > My problem in OOO 3.2 base (other front ends also) is that there is > continually a problem with not allowing queries to update data back to > postgresql. > > I believe something has changed perhaps in sql from 8.3 to 8.4, or I have > missed something with restoring the files. > > At minimum, we need to see the update statement that you are attempting to execute, preferably with any error message you receive. --bcaec51ddbe5fd5bd204a3f54135 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Mon, May 23, 2011 at 9:53 AM, Dean le= Roux <projserv= e@gmail.com> wrote:
postgres 8.3 to 8.4 =A0Open office base 3.2 Ubuntu 9.04 to 10.04 (new insta= ll)

I recently upgraded from Ubuntu 9.04 to Ubuntu 10.04. Security and other updates have been effected. I used webmin to restore the databases.

Since migrating to Linux around 2006 we were successful in converting our m= db
file to postgresql - only one glitch was a difference in -1 as YES. We
successfully used the systems with open office as a front end for the last = few
years. Until now - after the upgrade I can view data but not update data.
Experience with sql is very limited as I have always used sql query builder= s
over the years. The system has worked well with multiple tables, and in the=
past there was no problems with sending sql statements to postgresql.

My problem in OOO 3.2 base (other front ends also) is that there is
continually a problem with not allowing queries to update data back to
postgresql.

I believe something has changed perhaps in sql from 8.3 to 8.4, or I have missed something with restoring the files.



At minimum, we need to = see the update statement that you are attempting to execute, preferably wit= h any error message you receive.
--bcaec51ddbe5fd5bd204a3f54135--