• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Insert error with table hint / Autoincrement column

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (5)

Resolved Insert error with table hint / Autoincrement column

  1. Issue
0
Votes
Undo
  1. Jhonns Salas
    Jhonns Salas
  2. PowerBuilder
  3. Monday, 20 June 2022 07:19 AM UTC

Hello,

Our team is having a problem inserting a record in a table with a auto increment column(table hint),

I made a test in my workstation with PB R3, and i did not have any error in execution time,

but the group using PB R2 is not able to insert a record due to it is necessary to add a WITH keyboard to the insert statement.

It happens in execution time, not in design.

Do you know the cause of this issue or how solve it?

Thanks for your support.

Regards....

Attachments (2)
PB.jpg PB.jpg
pb 02.jpg pb 02.jpg
Migration from 11.5 to current PB, u_tab and Objec...
Selling my Successful PowerBuilder-based Business
Responses (5)
Jhonns Salas
Jhonns Salas Accepted Answer Pending Moderation
  1. Tuesday, 28 June 2022 14:39 PM UTC
  2. PowerBuilder
  3. # 1

Hello,

After we updated to PowerBuilder 2017 R3 Universal Edition, the problem was fixed,

but in the process i found different types of behavior of the application in both version.

For now the only situation to resolve is set the correct PB virtual machine DLLs files,

because in the application environment we cannot install the PB Packager,

could you please provide me an updated list of those files for PB 2017R3.

 

Thank you for the support,

Comment
John Fauss
  1. John Fauss
  2. Tuesday, 28 June 2022 15:27 PM UTC
Look in PB Help for the topic named "runtime files". It lists the runtime DLL's used by PB and what they are required for.
  1. Helpful
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Tuesday, 21 June 2022 13:18 PM UTC
  2. PowerBuilder
  3. # 2

I agree with Markus: drop the index hint.


If you choose not to do so, then put a breakpoint in the code JUST before the problem occurs. Copy the SQL and all associated variables.

In the database tool of your choice run the SQL and work with it. Often, these tools will provide more information than the PB runtime exe. Even the PB Database Painter gives you more information, and tools like Oracle's SQL Developer are even better at returning useful information.

Comment
There are no comments made yet.
Markus Eckert
Markus Eckert Accepted Answer Pending Moderation
  1. Tuesday, 21 June 2022 09:15 AM UTC
  2. PowerBuilder
  3. # 3

Hi Jhonns

Why do you even need an Index hint on an insert where you insert a single row using the VALUES construct?

I highly doubt that hint is even doing anything (except creating trouble in R2).

Regards,
Markus

Comment
Jhonns Salas
  1. Jhonns Salas
  2. Tuesday, 21 June 2022 15:31 PM UTC
Markus,



The Index hint depends from another system, in .Net, and i am not able to get rid of it,

I will making more testing, and try the R3 version.



Thanks and regards,
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 20 June 2022 15:41 PM UTC
  2. PowerBuilder
  3. # 4

Hi Jhonns ;

  FWIW: Sounds like the easiest &  simple fix is to get all the PB developers on the latest R3 MR.

Regards ... Chris

Comment
There are no comments made yet.
Andreas Mykonios
Andreas Mykonios Accepted Answer Pending Moderation
  1. Monday, 20 June 2022 07:53 AM UTC
  2. PowerBuilder
  3. # 5

Hi.

From what I read, the error should somewhere before the index=0. I would review and compare settings in ole db provider on your machine and machines where the insert fails. I would also compare the generated sql.

Andreas.

Comment
Load more comments
Andreas Mykonios
  1. Andreas Mykonios
  2. Tuesday, 21 June 2022 08:03 AM UTC
What troubles me in this case is that support for Microsoft OLE DB Driver (MSOLEDBSQL) was introduced in R3. So I agree with Chris that you should go on to R3. Of course this may not be easy to do immediately. You may need to do some testing... In my opinion there is something else in the syntax that cause the problem. You get a "generic" message. Database interfaces do return sometimes messages that may be misleading. In my opinion this could be the case.

Andreas.
  1. Helpful
Jhonns Salas
  1. Jhonns Salas
  2. Tuesday, 21 June 2022 19:20 PM UTC
Andreas,

A question, if OLE DB Driver (MSOLEDBSQL) was introduced in 2017 R3,

which build was that?

I suppose these drivers are more recommendable for Azure.

Thanks,
  1. Helpful
Andreas Mykonios
  1. Andreas Mykonios
  2. Wednesday, 22 June 2022 12:56 PM UTC
The MSOLEDBSQL that supports sql server up to 2019 was introduced in PB 2019 R3 initial release (2670, it was also available in beta but those runtimes are not intended for production). There was a MSOLE connector in previous releases, but the new one supports more features as far as I know. That may be the reason this issue happens only in lower versions than R3.

Andreas.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.