Recent Posts

81

Problems & Solutions / Re: COM OLE

« Last post by JRS on March 18, 2021, 04:03:36 PM »

it doesn't look like O2 supports VT_DISP. (iDispatch variant type)

Code: OxygenBasic

1. ' O2 Sage BOI
2.  
3. $filename "t.exe"                                    
4. uses  COM/COMutil                                    
5. CoInitialize null                                    
6. CreateInterfaceByName "ProvideX.Script" oscript
7. CallByName(oscript, "Init", BSTR {"C:\Sage\Sage 100 Standard\MAS90\Home"})
8. VARIANT va[2]
9.  
10. va.vt[1]=VT_BSTR : va[1].bstrval="SY_Session"        
11. va.vt[2]=VT_DISP
12. CallByNameV(oscript, METHOD, "NewObject", va, 2)
13. Print va[2].lval
14.  
15.  
16. oscript.Release                                        
17. CoUninitialize
18.  

82

Problems & Solutions / Re: COM OLE

« Last post by JRS on March 18, 2021, 12:37:25 PM »

I updated my firstcust.sb script to what I have installed on my Lenovo laptop.

Code: Script BASIC

1. ' Sage BOI (Business Object Interface)- first customer - selected columns
2.  
3. IMPORT COM.sbi
4.  
5. oscript = COM::CREATE(:SET, "ProvideX.Script")
6. COM::CBN oScript, "Init", :CALL, "C:\\Sage\\Sage 100 Standard\\MAS90\\Home"
7. osession = COM::CBN(oscript, "NewObject", :SET, "SY_Session")
8. COM::CBN osession, "nSetUser", :CALL, "js", "MY_PASSWORD"
9. COM::CBN osession, "nsetcompany", :CALL, "ABC"
10. COM::CBN osession, "nSetDate", :CALL, "A/R", "20171218"
11. COM::CBN osession, "nSetModule", :CALL, "A/R"
12. ocust = COM::CBN(oscript, "NewObject", :SET, "AR_Customer_svc", osession)
13. COM::CBN ocust, "nMoveFirst"
14. CustomerNo$ = COM::CBN(ocust, "sCustomerNo", :GET)
15. CustomerName$ = COM::CBN(ocust, "sCustomerName", :GET)
16. City$ = COM::CBN(ocust, "sCity", :GET)
17. State$ = COM::CBN(ocust, "sState", :GET)
18. TelephoneNo$ = COM::CBN(ocust, "sTelephoneNo", :GET)
19. COM::CBN ocust, "DropObject"
20. COM::CBN osession, "DropObject"
21. COM::RELEASE oscript
22.  
23. PRINT "Customer:  ", CustomerNo$, "  ", CustomerName$, "  ", City$, "  ", State$, "  ", TelephoneNo$, "\n"
24.  

C:\ScriptBASIC\sage>sbc firstcust.sb
Customer:  ABF  American Business Futures  Milwaukee  WI  (414) 555-4787

C:\ScriptBASIC\sage>


PowerShell's Measure-Command returns TotalSeconds      : 0.3442815 under ScriptBasic.

I'm working on converting this script to O2 COM/OLE.

I just noticed I wrote this original script on March 18, 2017.

83

Problems & Solutions / Re: COM OLE

« Last post by JRS on March 16, 2021, 10:02:50 AM »

Charles,

This BOI script example gets the first customer in the table / file and displays the selected columns.  (BOI is the Sage version of Dave's COM extension for SB.  BOI = COM)

How can I pass an iDispatch pointer with CallByName?  Sage has a NewObject method that can inherit other COM/OLE objects.

Code: Script BASIC

1. ' BOI - first customer - selected columns
2.  
3. IMPORT BOI.sbi
4.  
5. oscript = BOI::CREATE(:SET, "ProvideX.Script")
6. BOI::CBN oScript, "Init", :CALL, "C:\\Sage\\Sage 100 Advanced ERP\\MAS90\\HOME"
7. osession = BOI::CBN(oscript, "NewObject", :SET, "SY_Session")
8. BOI::CBN osession, "nSetUser", :CALL, "JRS", "MyPassword"
9. BOI::CBN osession, "nsetcompany", :CALL, "ABC"
10. BOI::CBN osession, "nSetDate", :CALL, "A/R", "20171218"
11. BOI::CBN osession, "nSetModule", :CALL, "A/R"
12. ocust = BOI::CBN(oscript, "NewObject", :SET, "AR_Customer_svc", osession)
13. BOI::CBN ocust, "nMoveFirst"
14. CustomerNo$ = BOI::CBN(ocust, "sCustomerNo", :GET)
15. CustomerName$ = BOI::CBN(ocust, "sCustomerName", :GET)
16. City$ = BOI::CBN(ocust, "sCity", :GET)
17. State$ = BOI::CBN(ocust, "sState", :GET)
18. TelephoneNo$ = BOI::CBN(ocust, "sTelephoneNo", :GET)
19. BOI::CBN ocust, "DropObject"
20. BOI::CBN osession, "DropObject"
21. BOI::RELEASE oscript
22.  
23. PRINT "Customer:  ", CustomerNo$, "  ", CustomerName$, "  ", City$, "  ", State$, "  ", TelephoneNo$, "\n"
24.  

Output

C:\ScriptBASIC\examples>scriba firstcust.sb
Customer:  ABF  American Business Futures  Milwaukee  WI  (414) 555-4787

C:\ScriptBASIC\examples>


It looks like I can use the CallByNameV() function when I need to pass a VT_DISP long variable.

84

Problems & Solutions / Re: COM OLE

« Last post by JRS on March 15, 2021, 04:14:59 PM »

I'm looking forward to getting VB6 events as callbacks to O2 for processing.

Charles,

Do you see any issues calling back to functions in the exe that started the program and calling the OCX? Will I need to use a DLL for callbacks including the COM\util tools?

85

Problems & Solutions / Re: COM OLE

« Last post by Charles Pegge on March 14, 2021, 10:30:57 PM »

Thanks John,

I will make CallByName a bit more flexible.

86

Problems & Solutions / Re: COM OLE

« Last post by JRS on March 14, 2021, 09:49:36 PM »

Success!

Note: ScriptBasic is providing the Windows style support. (both SBC & SBW are compiled with style support)

Thanks Charles for all your effort in getting COM / OLE automation working in O2.

87

Problems & Solutions / Re: COM OLE

« Last post by Charles Pegge on March 14, 2021, 09:15:23 PM »

Okay.

Try CmdByName instead of CallByName. This is for calls that have no params

88

Problems & Solutions / Re: COM OLE

« Last post by JRS on March 14, 2021, 03:44:24 PM »

No error and returns a handle.

89

Problems & Solutions / Re: COM OLE

« Last post by Charles Pegge on March 14, 2021, 03:35:40 PM »

Can you see whether it has given you an interface:

Code: [Select]

    ' O2 VB6
     
    $filename "mlink.exe"
    uses  COM/COMutil
    CoInitialize null
     
    CreateInterfaceByName "MASLink.OCXForm" mlobj
print err
print @mlobj
    CallByName(mlobj, "ShowOCXForm")
     
    mlobj.Release
    CoUninitialize

     

90

Problems & Solutions / Re: COM OLE

« Last post by JRS on March 14, 2021, 12:34:10 PM »

Your updated O2 allows the above example to work. No luck with my VB6 OCX form.

It seems O2 isn't happy about the OCX taking over leaving O2 waiting for it to close. (guess) I will try and create a simple one button form with no SB dependencies and see if that works.