and my last suggestion:

Activate Tracing by Adding "TRACE " before whatever you have in your sqlca.DBMS value. See if it catches some error before the error.

Which sqlca.DBMS? It seems you are using ODBC? (since you have an entry for "pbNewSPinvocation" set to yes in your dbparm? What database are you using?

Do you rely on the distribution / presence of maybe pbodb190.ini?

If so, remember that in 2019 R3, this filename now should be named PBODD.INI, without any numbers in the name.

regards

Have you checked the values of all your variables in line 106 in debugger right before line 110 to be sure none are null?

@user_name = :ls_user, @date = :ldt_now, @pm = :is_pm, @alt1 = :is_alt1, @alt2 = :is_alt2

I know you said it worked before, but as Chris mentioned, maybe the timing of events has changed slightly and one of those variables is null.

 "ConnectString='DSN=EpicEsso;UID=pbuser;PWD=pbuser',CallEscape='No',DisableBind=1,DisableUnicode=1,Maxconnect=250,PBNewSPInvocation='yes'"

1. Yes, it runs on the SQL database without error.

2. Yes, the parameters are the same as before. No change.

3. Yes, SQLCA is valid.

4. Made no difference.

5. Yes, rights were verified.

6. Yes, variables hold appropriate values. Verified.

Thank you for your response. This new version is killing me. There are other odd things that are happening that I do not understand their cause. I've never had the slightest problem with a PB upgrade until this version. 

Did 2 full re-compiles before creating this message. Each time the user and I still see the same message as originally entered. 

Thank you for your response.

Hi Clifford,

It seems that the error message you provided isn’t matched with the 110 line code.

I suggest you:

1. Reinstall PB 2019 R3 IDE and then Full Build your application to see if the same error exists.
2. Can you find out something new if you debug your application? 

Regards,

Ken

Hi,

1. Can you run the stored procedure "outside" of powerbuilder? Like in Oracle Sql Developer or Microsoft Management Studio. (maybe it needs recompiling)

2. are your sqlca dbparm parameters the same as before?

3. are you connected when the code runs, is SQLCA valid?

4. try declaring the stored procedure without the "dbo."

5. do you have the proper rights for the user to execute this stored procedure?

6. Do your variables all hold an appropiate value? Is there any OUT parameter?
@user_name = :ls_user, @date = :ldt_now, @pm = :is_pm, @alt1 = :is_alt1, @alt2 = :is_alt2

That's all I can come up with for now,

regards

Hi Clifford;
   I would recommend using the PB IDE's "debugger" to step through your code.

   Note that R3 has changed a few events like the Activate and Open "timing" wise. So you may need to wrap your code in an IsValid() command. Food for thought.

Regards ... Chris

what error information does SQLCA contain after the declare?