| Paul Fast 2005-04-25, 8:24 pm |
| Are you using MVB (i.e. with VB6) or Crossfire (with .NET)? I've heard some
similar problems when using Crossfire. Generally completely unregistering
and then re-registering addresses the problem. Here are the steps
1. Open a command prompt and go to
%asany9%\ultralite\u
ltraliteforMobileVB\
win32
2. Run ulmvbreg -u (this unregisters the component but .NET leaves a few
things hanging around)
3. Start .NET and create a new Crossfire project (choose a UL-compatible
target like 160x160 Palm OS)
4. Right click on the toolbox/tools palette and select "Add/Remove
Items..."
5. On the ".NET Framework Components" tab, scroll down to ULConnectionParms
in the iAnywhere.UltraLiteIngots namespace and deselect it. Click OK (it
should no longer appear in the tools palette).
6. Shutdown .NET (it doesn't matter if you save your project)
*** this should remove all traces of the component ***
7. From the command prompt again, type ulmvbreg -r (this should register
your component)
Hope this helps.
Paul
<Mike S> wrote in message news:42694c76.61f9.1681692777@sybase.com...
>I was working fine with Mobile VB 5.6.0 and ASA 9.0.1.
> Aftere I upgraded to 9.0.2.3044, the Ultralite object
> ULConnectionParms gives the error: Component not correctly
> registered. I tried registering ulmvbctl9.dll manually but
> still no luck. Any ideas?
|