|
-
Feb 8th, 2000, 06:34 PM
#1
Thread Starter
Frenzied Member
-
Feb 8th, 2000, 10:50 PM
#2
Addicted Member
And they are backwards compatible (at least that's what is intended).
------------------
Jorge Ledo
[email protected]
Portugal
-
Feb 8th, 2000, 11:48 PM
#3
I think you will find the following Knowledge Base article interesting. 
Q192934. I can't tell from your post if your problem is the same as the one my company ran into, but here is what happened to us. A VB5 app of mine was running just fine on all PCs when all of a sudden we got reports of people getting 3447 errors when starting up. After a lot of investigation and with the help of the article above, we determined that another app which was developed using Visual Studio 6 was force-loading the Visual Studio 6 DLLs. Once the setup for that app was modified, the problem went away.
------------------
Marty
What did the fish say when it hit the concrete wall?
> > > > > "Dam!"
-
Feb 10th, 2000, 07:43 AM
#4
New Member
I've got a user with the same problem. I took the above advice and sent the older version of the DLL with instructions on unregistering and all, but when she tries to unregister, it "fails".
I tested on my machine and I get the same results. I've shut everything down, clean booted, and still the same thing. Any ideas?
TIA
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|