Thanks Dave, I'll give it a shot and let you know how I make out.

I have written and currently maintain a VB6 legacy app for a client. There are thousands of copies running successfully all over the world... with one exception. One of my client's customers installed the software on a WIN7 system and gets the RTE 339 - tabctl32. The weird part is that if he boots in safe mode, it works perfectly. I have told my client to use regsrv32 in admin mode to un-register and re-register the ocx. He gets a successful completion when doing so but still gets the RTE 339 error. I have had the client run "Handle.exe" to see if any process that loads during a normal startup might have a lock on the ocx but the results show nothing. Anyone have any ideas as to why this would work in safe mode but not on a normal boot?

I was having the same problem. the /codebase switch made it work. Thanks!