HELP PLEASE -- Run-time error '458': Variable uses an Automation type not supported in Visual Basic.

This error is driving me insane. Whenever the client (EXE) calls the server
object (DLL) on a MTS box, the client crashes with a r/t error 458. Has
anyone ever seen this?. There are absolutely no UDT's. The methods return
ADODB RecordSets, and I can not get arround this. In the development
envrionment, it works fine, on the test WTS server, it works fine; on one of
the two production WTS servers, it works fine. BUT there is that one
production WTS server that is not going to work at all. This leads me to
believe that there is a registry problem. What should I look for in the WTS
machine's Registry?

TIA --

BillG

I have had this once with default values on optional parameters. I think it
was an optional variant with default value Null. Luckily for me I knew what
the last change was before I got this error. Hope it's that simple with you
too.

--
Van den Driessche Willy
For a work in progress :
http://users.skynet.be/wvdd2/index.html

I ran into this same problem some time back. It turned out to be different
versions of SCRRUN.DLL on the two systems. I replaced the (older) version
on the production system with the (newer) version from development and it
worked fine.

Mike

"Bill Gauvey" <bill.gauvey@@acxiom.com> wrote:
>This error is driving me insane. Whenever the client (EXE) calls the server
>object (DLL) on a MTS box, the client crashes with a r/t error 458. Has
>anyone ever seen this?. There are absolutely no UDT's. The methods return
>ADODB RecordSets, and I can not get arround this. In the development
>envrionment, it works fine, on the test WTS server, it works fine; on one
of
>the two production WTS servers, it works fine. BUT there is that one
>production WTS server that is not going to work at all. This leads me to
>believe that there is a registry problem. What should I look for in the
WTS
>machine's Registry?
>
>TIA --
>
>BillG
>
>

Yes! Thank you, I had an optional variant parameter with default value Null
and that was the problem. This must be a bug?

>was an optional variant with default value Null. Luckily for me I knew



JF

"John Fleming" <jfleming@morneausobeco.com> wrote in message
news:3c20b753$1@147.208.176.211...
>
>
> Yes! Thank you, I had an optional variant parameter with default value
Null
> and that was the problem. This must be a bug?
>
I have little doubt this is a bug. I'm glad you could solve your problem.
I also learned it the hard way.

See you
--
Van den Driessche Willy
For a work in progress :
http://users.skynet.be/wvdd2/index.html