Results 1 to 4 of 4

Thread: F*****G 3447!!!!

  1. #1

    Thread Starter
    Frenzied Member Mark Sreeves's Avatar
    Join Date
    Nov 1999
    Location
    UK
    Posts
    1,845

    Post



    HELP!

    This is REALLYbegining to P*** ME OFF!

    My app was written in VB5
    I have NOT got VB6 on my this PC
    so all microsoft's suggestions are just bullshit!

    I issued DAO350.dll version 3.50.3602.0 in the istalation program.

    A user (in Germany) cannot run the installed software.

    He has only one DAO350.dll on his PC and that is version 3.51.1608.0

    I've got him to re-register it but still no luck.

    I emailed him DAO350.dll version 3.50.3602.0 with instructions to unregister and rename his original dll and register this one.

    This WORKED!

    I suppose I'll have to wait and see what app was using version 3.51.1608.0!


    Surely dlls with a higher version number sould be backwardly compatable?!



    ------------------
    Mark Sreeves
    Analyst Programmer

    [email protected]
    A BMW Group Company



    [This message has been edited by Mark Sreeves (edited 02-09-2000).]

  2. #2
    Addicted Member
    Join Date
    Oct 1999
    Location
    Oporto, Portugal
    Posts
    134

    Post

    And they are backwards compatible (at least that's what is intended).



    ------------------
    Jorge Ledo
    [email protected]
    Portugal

  3. #3
    Former Admin/Moderator MartinLiss's Avatar
    Join Date
    Sep 1999
    Location
    San Jose, CA
    Posts
    33,431

    Post

    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!"

  4. #4

    Post

    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
  •  



Click Here to Expand Forum to Full Width