Hi Chris,

Thank you for your programming lines.

I have already created a WPF project and combined Class.cbl with the content you sent me.

I have already made the necessary adaptations and carried out some tests.

Apparently everything will be working.

Now I have to improve some features to be 100% effective.

There is a situation that I will have to implement but I haven't been able to see how yet.

I have to find a way to cancel the process (CANCEL) while I'm in the machine query cycle to see if it's already finished.

I have a window with an AMOUNT field, a PAY button and a CANCEL button.

I enter the amount and click PAY. While the machine is waiting for the customer to enter the money, I may have to cancel the process.

Considering that the CANCEL button is in the main program, if I click on CANCEL, will the program detect this CANCEL?

Thank again.

The general technique you're looking for in WPF is to use a background thread for the processing instead of doing the work on the UI thread (where the button is). If it is done on the UI thread, the button will be frozen until the process returns back. This is something you will need to read up on for .NET/WPF.  This concept has been around for quite some time in .NET/WPF

Hi Chris,

Now that I have all the tests done, I'm trying to integrate the development I did (WPF project) into my application.

I copied the "cashClass" to the general project and I'm trying to copy the part that makes the "call" to the cashClass in the application.

I created a "method-id" in the invoice issuing source containing the part of the call to "cashClass".

As this call has an "await", the method-id has to be async so I created it like this "method-id bus_alice public async".

After issuing the invoice, I invoke this method with "invoke self::bus_alice()".

In terms of compilation, there is no error. When I run the application, this invoke gives the following error:

If you create the method as "method-id bus_alice public async-void.", it also doesn't give compilation errors but it still gives an error:

I don't know what to do. I've tried everything.

I am attaching the test project so you can check what I am trying to do. I integrated the "cashClass" into my project without any problems (for now).

The real issue is the part of calling the class.

Best regards

Hi Alberto,

I ran your test project using V10.0 and it all worked perfectly.

I will test it with the version you are using which is V8.0 to see if the problem is there.

Actually, it runs fine under V8.0 as well but I dont see the method on which you are getting the error.

Is there something I am supposed to do to the code in order to make it fail>

Actually, it runs fine under V8.0 as well but I dont see the method on which you are getting the error.

Is there something I am supposed to do to the code in order to make it fail>

I'll try to make a better explanation of the problem I'm having.

I will send it in a next post.

Hi Chris,

In the meantime, I opted for another strategy but it is also causing problems.

Instead of integrating the lines into the invoicing program, I chose to make a call to a .xaml (WPF window).

In that .xaml, then place the instructions to access the equipment's API.

But instead it returns to the invoicing program with the following error:

I copied the lines from the test project I sent you.

Apparently everything should be correct but it isn't.

I will attach the new .xaml with the respective window.

It is this .xaml that I call from the billing program.

Note: what I'm reporting is all included in the same project.

I hope you can help me once again.

Thanks.

Can you please provide the required copybooks for the new program?

They are attached.

Still missing LNKREC.CPY.

Sorry...

The problem appears to be caused by the SQL(DBMAN=ODBC) directive on in the Call_Icash.xaml.cbl program. If I comment out the directive and the statements referencing SQL syntax then it seems to work fine.

I will look into the cause more, but it is recommended that instead of embedding SQL statements directly in a WPF class that you instead put it into a separate class or COBOL program and call it from the WPF app.