We got around this one by creating a VB6 DLL that implemented only the functionality we needed (file open and close, record read, DynArray field/value/mv and oconv/iconv. If you are planning to use a lot of functionality then it is a pain in the neck but if you only use a little (like we do) then it a relatively painless way to get around things.
The only warning I would give is that our code worked great when it ran with the push of a button on a form, but when we turned it into a Windows Service it refused to get out of bed - everything ground to a halt at the first UO call. It might have been something I did, though. We are using UniData 5.1 on DG/UX. Peter Welsh Senior IT Development Officer NHS Greater Glasgow & Clyde [snip] I am converting some VB6 code with UniObjects to VB.NET (2005). The following The third statement is the one that works on VB6 but take the On Error routine in .NET. Can someone explain to me what the problem is? (Yes, I could code around this, but this kind of thing is done a lot in this code--not my code, BTW ☺ Thanks for any insight. -- Regards, Clif ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
