Thanks, David, this was actually the most helpful suggestion. Using logging of SQL statements in Postgres, I was able to first determine that the style of quoting I was using in the PowerBuilder INI file wasn’t working, and then that the &TableName variable wasn’t being expanded by PowerBuilder before sending the SQL to Postgres. The latter of which is a clear PowerBuilder problem, so I have submitted it to them as a bug.
So I think we can now put this to rest on this mailing list. Thanks, all.
--------------------------------------------------------
Dan Cooperstock
DONATION and ACCOUNTS web site: http://www.Software4Nonprofits.com
Email: info@xxxxxxxxxxxxxxxxxxxxxxx
Phone: 416-423-7722
Mail: 57 Gledhill Ave., Toronto ON M4C 5K7, Canada
If you do not want to receive any further emails from Software4Nonprofits, please reply to this email with the subject line "UNSUBSCRIBE", and we will immediately remove you from our mailing list, if you are on it.
From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of David G. Johnston
Sent: August 6, 2017 3:47 AM
To: Dan Cooperstock at Software4Nonprofits <info@xxxxxxxxxxxxxxxxxxxxxxx>
Cc: Forums postgresql <pgsql-general@xxxxxxxxxxxxxx>
Subject: PostgreSQL with PowerBuilder, and Identity keys (serials)
On Saturday, August 5, 2017, Dan Cooperstock at Software4Nonprofits <info@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
As I have mentioned in several replies, I have tested all of this code
directly in SQL statements and they work perfectly. It's only the
interaction with PowerBuilder that isn't working right, which is why I keep
saying that further answers from anyone that hasn't solved this problem of
using Postgres with PowerBuilder, and getting identity retrieval to work in
PowerBuilder, are not at this point worthwhile.
If it is PostgreSQL's problem you should be able to setup statement logging on the server and see what is happening at the SQL level.
