Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies replies
    4
  • Answers answer
    1
  • Subscribers subscribers
    9
  • Views views
    763
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

While connecting with Rumba 10 using VB6 automation error facing

MANGESH ANASANE

We have written code for connecting rumba app with our app. Earlier it has working fine with Rumba 8.1 Version. After upgradation version of Rumba 8.1 to 10.1 its gives automation error. Same code not working with Rumba 10.1 Version. Any help will be much appreciated. 

Labels:

Rumba
  • 0  

    Hello Manesh,
    can you please elaborate a bit on your problem.

    - How do you connect with RUMBA in your VB Application. What API is used?
    - Do you get an Error Message? Explain what you mean by automation error.?
    - Did you just upgrade the RUMBA version or are more changes involved?
    - Can you please provide a code snippet to see what is failing.

    If you can't share the information in this forum, please open a case with our support team (https://portal.microfocus.com). The team will work with you to resolve your issue.

    cheers

    andree

  • 0 in reply to   

    Hi Andree We have Written VB6 code for that 

    please find the below block for that , in that it will stuck on doevent it will throws automation error.5706.Code of Rumba Connect Screenshot.docx

    ObjMFDisplay.Connect
    DoEvents
    If ObjMFDisplay.Connect = False Then ' Connects the Display control
    waitAWhile (20)
    ObjMFDisplay.Disconnect
    waitAWhile (20)
    ObjMFDisplay.Connect
    DoEvents
    If ObjMFDisplay.Connect = False Then ' Connects the Display control
    waitAWhile (20)
    End If
    End If
    If Check_Screen(22, 57, 4, "===>") = False Then
    waitAWhile (20)
    ObjMFDisplay.Disconnect
    waitAWhile (20)
    ObjMFDisplay.Connect
    DoEvents
    If ObjMFDisplay.Connect = False Then ' Connects the Display control
    DoEvents
    ObjMFDisplay.Disconnect
    DoEvents
    ObjMFDisplay.Connect
    DoEvents
    If ObjMFDisplay.Connect = False Then ' Connects the Display control
    DoEvents
    ObjMFDisplay.Disconnect
    DoEvents
    ObjMFDisplay.Connect
    DoEvents
    If ObjMFDisplay.Connect = False Then ' Connects the Display control
    DoEvents
    MsgBox "Unable to get to Signon Screen", vbCritical + vbOKOnly
    Exit Sub
    End If
    End If
    End If
    End If

  • Verified Answer

    +1 in reply to 

    - Did you just upgrade the RUMBA version or are more changes involved?--- Yes we have upgraded Rumba 8.1 to 10.1

    -Can you please provide a code snippet to see what is failing. --- Doevent 

  • Suggested Answer

    0   in reply to 

    Hello Manesh,
    this type of request are difficult to handle in the forum but the support teams can work with you.
    Could you please open a ticket with the support team to assist you in the best possible way.

    I can replicate a Run-time error '-1 (ffffffff), but it only occur in the VB 6 IDE. After I compile the project I have no issues.
    I'm sure you're aware but Visual Basic 6.0 IDE or Visual Studio 6.0 IDE as a whole moved out of extended support on April 8, 2008 by Microsoft.

    If you're going to open a case please make sure the problem occurs in the runtime.
    it would help us f you provide a simple VB6 project code to reproduce your error.


    cheers

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.