The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: Re: Re: Proposal / RFC: Change xAP wire format


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

xapax.ocx with VBScript


  • Subject: xapax.ocx with VBScript
  • From: "Taras" <tartheode@xxxxxxxxx>
  • Date: Fri, 02 May 2008 20:11:20 -0000

I plan to develop a xAP driver for a home automation program
called "Premise Home Control".  Premise's native scripting
language
is VBScript.

I tried to use Patrick Lidstone's "xapax.ocx" with VBScript but
haven't made any progress.

The following works well in VBA (I tried it in Excel):
Public Sub test()
Dim xpx As New Xapax
MsgBox xpx.Version
End Sub
A message box pops up and displays "v.3.0 (Build 17)". OK!

I tried the following with VBScript:
set xpx = wscript.CreateObject("XAPAX.XapaxCtrl.1",
"xpx_")
wscript.echo xpx.Version
The result is a dialog box indicating a "Catastrophic Failure" on
line 2, character 1. Not OK!

It doesn't fail at the "CreateObject" statement but when you try
to
use the instantiated object "Xpx".  Either I'm doing something
wildly
wrong or xapax.ocx cannot be used by VBScript (or it just doesn't
like Windows Script Host).

Any ideas where the problem lies?  Any alternate solutions that'll
work with VBScript?






------------------------------------


xAP_Development Main Index | xAP_Development Thread Index | xAP_Development Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.