Hi there,
Powerbuilder 12.5 classic application has no issues creating temporary tables in an Azure MSSQL database (account dbo user) but for some unknown reason... a deployed web application from PB 12.5 using the same connection parameters (user name/password) suddenly does not have 'CREATE' permissions.
Tried it with an ADO.NET and SNC.... no joy ;(
Any suggestions ?
Thanks in advance
Yes, Autocommit is set to TRUE in the transaction object. (set via same INI file web/non-web)
It's an 'embedded' CREATE command (powerscript)
// create temporary table
ls_temp = "CREATE TABLE #ipas_pension_summarization " + &
"(calendar_year decimal(4,0) NOT NULL, " + &
"contribution_rate decimal(10,4) NOT NULL, " + &
"effective_months decimal(10,4) NOT NULL, " + &
"months_to_distribute decimal(4,0) NOT NULL, " + &
"employer_code varchar(5) NOT NULL, " + &
"schedule_id decimal(10,0) NULL)"
EXECUTE IMMEDIATE :ls_temp;
Works fine from a local compiled app... but not when deployed as a web app. Does APPEON play with the autocommit at connection time ?
Can you elaborate on the #TempTable route ?
Thanks in advance,
Pierre
I just realized that your were talking about a PowerServer WEB based application. PS does support the AutoCommit setting. So I am not sure why Azure's SQL Server would not comply. Could be a "Borg" issue! ;-)
I would suggest opening a Support Ticket for this issue. As a workaround though ... what about using a Stored Procedure instead to create the TempTable?
Regards ... Chris