Jump to content


Mobilize.Net Staff
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About OlmanQuesada

  1. MultiDimensional Array with ArraysHelper

    Thanks Kevin, I'm glad to hear the issue is gone. As you mentioned, by just modifying the property return type would fix the issue. Cheers, OlmanQ
  2. MultiDimensional Array with ArraysHelper

    Thanks Kevin, Could you please include the definition of mobjEmployeeL2.EmployeeArray in both languages VB6 and C#, and the definition of astrGridData in vb6? OlmanQ
  3. MultiDimensional Array with ArraysHelper

    Hi Kevin, Could you send us a code sample where this error is happening? Please includes all variables definitions. Regards, OlmanQ
  4. rs.Properties("Unique Table")

    Hi Michael, ADO.Net does not provide a direct way to achieve that, so the migrated code should be modified to get a similar result. As the ADORecordsetHelper inherits from a Dataset, the properties of that class could be used: Given rs is a ADORecordsetHelper you can try the following: DataRow rowDel=ds.Tables["table1"].Rows[<IndexOfTheRowToDelete>]; rs.Tables["table1"].Rows.Remove(rowDel); rs.Delete() Cheers, OlmanQ
  5. rs.Properties("Unique Table")

    Hi Michael, Could be that possible to give us more context about the code. Perhaps a small VB6 sample code. Regards Olman Q
  6. license fingerprint

    Hi Marco, Let's continue with this support via email. I'll contact you at the email indicated in your profile. Olman Q
  7. license fingerprint

    Hi Marco, Thanks for the info. Our License department is asking for the license info. This cab be got from the VBUC in the menu Tools->License Info. If you can send me a screenshot that would help to track the info for that license. Regards Olman Q
  8. license fingerprint

    Hi Marco, Could you please indicate me on behalf of whom is the license. I'm asking this in order to generate a new license with the exact information. Regards
  9. VBU.exe has encountered a problem and needs to close...

    Hi Jamie, Sorry for the delay. The Helpers are written in C#, so when the code is migrated to VB.Net, the VBUC switches the "Helper Integration" option to binary, but you can change it back to "Source Code". We've found the error is not present when the code is converted to a newer version of VS.Net (like 2013/2015). Regards, Olman Q
  10. license fingerprint

    Hi Marco, I think the VBUC.Lic file may be corrupted. I'm resending to you a trial versions license to migrate up to 10K lines of code, please check your email. Please, re-install the VBUC and use the attached Trial_VBUC.Lic to activate the trial version. Regards
  11. license fingerprint

    Hi Marco, I need some additional info in order to reproduce the issue. Could you please indicate which OS are you running on? Any other useful information about how you get this error would be helpful. Another option. You can try installing and running the VBUC (using admin rights) in a fresh machine. Regards, Olman Q
  12. license fingerprint

    Hi Marco, Please make sure to run the Visual basic Upgrade Companion (VBUC) using admin rights. Can you provide us with the version number of the Visual Basic Upgrade Companion (VBUC)? You can get this by opening the VBUC and then click on the upper left arrow and select the About option. Cheers OlmanQ
  13. VBU.exe has encountered a problem and needs to close...

    Hi Jamie, Could be that possible for you to share with us additional information about variables/properties declared in this form:SGIInvoicing.frmSGIInvoicing. In addition, please try migrating the application to Visual Basic .Net by setting the "Helpers Integration" option to "Source Code" rather than "Binary". regards, OlmanQ
  14. VB6 Migration to C#(VS2015)

    Hi Rohit, In general, the VBUC try to use .Net native libraries, but there are some cases we need to use those compatibility libraries because there isn't a straightforward .Net approach. You can modify any portion of the generated code (C$ or VB.Net), including the helpers. Cheers, Olman Q
  15. VB6 Migration to C#(VS2015)

    Hi, Could you please indicate which methods you don't want to be used via the Microsoft.VisualBasic.Compatibility assembly? Regards, Olman Quesada