Prev: Money 2.3.0
Next: Newbie ruby watir exception handling
From: Masaki Suketa on 16 Apr 2010 11:13
Sorry for beeing too late to reply.

On Tue, Jan 26, 2010 at 08:33:18PM +0900, Tallak Tveide wrote:
> Masaki Suketa wrote:
> > Ooops,
> >
> > On Sat, Jan 23, 2010 at 07:15:21AM +0900, Masaki Suketa wrote:
> >>
> >> How about using WIN32OLE_VARIANT?
> >>
> >> items = WIN32OLE_VARIANT(null, WIN32OLE::VARIANT::VT_NULL)
> >> errors = WIN32OLE_VARIANT(null, WIN32OLE::VARIANT::VT_NULL)
> >
> > items = WIN32OLE_VARIANT.new(nil, WIN32OLE::VARIANT::VT_NULL)
> > errors = WIN32OLE_VARIANT.new(nil, WIN32OLE::VARIANT::VT_NULL)
> >
> > Regards,
> > Masaki Suketa
>
> Sorry - no help. The code now looks like this (without olegen):
>
> items = WIN32OLE_VARIANT.new(nil, WIN32OLE::VARIANT::VT_NULL)
> errors = WIN32OLE_VARIANT.new(nil, WIN32OLE::VARIANT::VT_NULL)
> group.OPCItems.AddItems 1, ['', 'Random.Int1'], [0, 1], items, errors

How about VT_EMPTY instead of VT_NULL?
items = WIN32OLE_VARIANT.new(nil, WIN32OLE::VARIANT::VT_EMPTY)
errors = WIN32OLE_VARIANT.new(nil, WIN32OLE::VARIANT::VT_EMPTY)
group.OPCItems.AddItems 1, ['', 'Random.Int1'], [0, 1], items, errors

Regards,
Masaki Suketa

From: tallakt on 20 Apr 2010 08:32
> How about VT_EMPTY instead of VT_NULL?

This yields the same results as the example above.

Thanks again for your help ;-)

Tallak
 | 
Pages: 1
Prev: Money 2.3.0
Next: Newbie ruby watir exception handling