Skip to main content

Hi, every one

I'm having an issue with an Acucobol application where the error shown in the attached photos appears. This error only occurs for one user who connects to the application using an Android tablet and a remote desktop client. The rest of the users who connect to the application via terminal service do not experience this problem, so I believe it must be something related to the tablet's connection. If anyone could provide me with some information regarding this, I would greatly appreciate it.

Thank you very much.

Hi, every one

I'm having an issue with an Acucobol application where the error shown in the attached photos appears. This error only occurs for one user who connects to the application using an Android tablet and a remote desktop client. The rest of the users who connect to the application via terminal service do not experience this problem, so I believe it must be something related to the tablet's connection. If anyone could provide me with some information regarding this, I would greatly appreciate it.

Thank you very much.

We don't have an environment to test (or debug) this, so it is hard to comment. But I suggest that if a problem happens in a single environment, then it is likely to want to blame the environment.

I suspect that if we did have an environment to play with this, we would discover that some Win32 API call we are making is failing in an unexpected way. Which we may or may not be able to do anything about.


We don't have an environment to test (or debug) this, so it is hard to comment. But I suggest that if a problem happens in a single environment, then it is likely to want to blame the environment.

I suspect that if we did have an environment to play with this, we would discover that some Win32 API call we are making is failing in an unexpected way. Which we may or may not be able to do anything about.

Thanks for answer


Hi, every one

I'm having an issue with an Acucobol application where the error shown in the attached photos appears. This error only occurs for one user who connects to the application using an Android tablet and a remote desktop client. The rest of the users who connect to the application via terminal service do not experience this problem, so I believe it must be something related to the tablet's connection. If anyone could provide me with some information regarding this, I would greatly appreciate it.

Thank you very much.

Good afternoon, Fernando javier Suárez escuela 

In 10.x, we have release AcuToWeb.

Introducing extend 10.1 & AcuToWeb
https://community.rocketsoftware.com/blogs/ed-airey/2017/02/01/introducing-extend-101-acutoweb 

extend Product Guides > AcuToWeb Version 10.5.1 User's Guide
https://www.microfocus.com/documentation/extend-acucobol/1051/extend-interoperability-suite/GUID-5F49ACE6-FCB9-4F41-873A-7A65DCCECA1B.html 

I suggest you to talk with your local Account Manager.

Or to submit a Case to the Customer Support portal - https://portal.microfocus.com/ 

We'll be very happy to show you this new technology, dedicated to a mobile-based client-server environment.