Problems with VBA using Excel 2003 (missing DLL's)

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • andylucky
    New Member
    • Oct 2011
    • 5
    #1

    Problems with VBA using Excel 2003 (missing DLL's)

    Hi everybody,

    About 5 years ago I created a program using Visual Basic in Excel 2003. This has always worked perfectly in our company.
    Problem now is that one of the pc's it ran on has crashed, I re-installed Windows XP, and Office 2003 with original disks but when running this excel file is gives an error concerning missing DLL's but does not say which one.
    The program still works on the other pc's so it must be something with the installation of Office I think.

    I noticed that .NET is also installed upto version 4.
    Could that be the culprit ?

    Anyone got any ideas as to what could be going wrong.

    Thanks a lot for your info.
    Andy
    Tags: None
    • Guido Geurs
      Recognized Expert Contributor
      • Oct 2009
      • 767
      #2
      Is it possible to install XP and office 2003 on a blanco new PC without .net?
      Run the VB program and=>
      - If it's not working then you are missing DLL's who are not in the original packet.
      - If it's working, then the software XP and office is OK and is on the original PC the DLL deleted or overwritten with a new version in which the called functions in the VB are not present or changed ?.

      Do you have the source of the VB program?
      Are there function call's?
      Are all the DLL's in these call's present?
      Are there References linked?
      Are these DLL's present?

        Comment

        • andylucky
          New Member
          • Oct 2011
          • 5
          #3
          Guido, thanks for your reply.
          Here is your answer with my comments.
          Weird that it works on all other machines.
          Andy

          Is it possible to install XP and office 2003 on a blanco new PC without .net?
          Not possible as the .net is neccessary for another program.Run the VB program and=>
          - If it's not working then you are missing DLL's who are not in the original packet.
          - If it's working, then the software XP and office is OK and is on the original PC the DLL deleted or overwritten with a new version in which the called functions in the VB are not present or changed ?.

          Do you have the source of the VB program?
          Yes, I wrote it myself
          Are there function call's?
          The first error mentioned is when I try to give a variable a value
          Are all the DLL's in these call's present?
          That's the problem, which DLL's are missing and which do I need ?
          Are there References linked?
          Are these DLL's present?

            Comment

            • Guido Geurs
              Recognized Expert Contributor
              • Oct 2009
              • 767
              #4
              - By a blanco PC I mean an other PC: new or old with nothing on the HD.
              Just for testing XP, office and your program.

              - A variable in a "Declare function..." or a variable "Dim"med by your own?

                Comment

                • andylucky
                  New Member
                  • Oct 2011
                  • 5
                  #5
                  Guido,
                  Ik heb geen 'lege' pc beschikbaar.
                  De code dat een fout geeft is....
                  datetot = DateSerial(2010 , 2, 10)
                  Met deze variabele (datetot) ga ik de datum van vandaag verglijken en naargeland eerder of later wordt er een bericht getoond.
                  Heeft jaren gewerkt, nu met deze pc (na her-installeren) niet meer.
                  Wat nog raarder is dat als ik deze sub-routine en de call ernaartoe verwijder werkt het nog niet, geeft steeds melding ivm dll's.
                  Ik heb nu .net versie 4 er vanmorgen verwijderd en ga straks proberen met Office 2003 opnieuw te installeren. Misschien dat dit werkt.
                  Alvast bedankt voor je tijd en raad.
                  Andy

                    Comment

                    • Guido Geurs
                      Recognized Expert Contributor
                      • Oct 2009
                      • 767
                      #6
                      Please Andy, can we continue in English ? (house rule of Bytes) so everyone can read it and learn from our problems and solutions.

                      Do you know the "Object browser" in VBA ?
                      It tells us in which DLL the function "Dateserial " is found. (see attachments)

                      Dateserial is in the VBA DLL location: (click on the green VBA at the bottom)
                      C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6 \VBE6.DLL
                      Is this file OK?
                      Attached Files

                        Comment

                        • andylucky
                          New Member
                          • Oct 2011
                          • 5
                          #7
                          Guido,

                          Sorry for the Flemish text, I forgot for a moment that others might also read this.
                          Appologies to all readers.

                          My problem is solved !
                          How did I solve it ?
                          As I said, yesterday I removed .net version 4 (VBA still gave errors)
                          This morning I removed Office 2003 and re-installed it (VBA still gave errors)
                          I installed service pack 2 from disk (VBA still gave errors)
                          I installed service pack 3 from MS-site (VBA works)

                          Thanks again for taking the time to read and reply to my messages.
                          I'll certainly be back if I need more help on VBA in the future.

                          Kind regards,
                          Andy

                            Comment

                            Previous template Next
                            Working...