Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

MSVBVM60.dll Not found

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    MSVBVM60.dll Not found

    Guys:

    I'm not a user of blinking fields and have had no real printer issues with the new verson.

    I thought, Why not? - I'll just keep everyting up to date and loaded Selwyn 701 Patch. When I clicked A4.[exe] I got the above windows' error message. I'm sure it's something I did wrong.

    Ken

    #2
    RE: MSVBVM60.dll Not found

    Ken, here's a wild guess...perhaps you aborted the installation routines prematurely? I suggest you reboot and try again. -- tom

    Comment


      #3
      RE: MSVBVM60.dll Not found

      Ken:
      attached is the msvbms60 file.
      put it in the windows system directory

      one other thought: if you already have the file, then it might be a path problem.
      if you already have it in the windows system folder copy it to the directory where you installed version 7

      Charlie Crimmel

      Comment


        #4
        RE: MSVBVM60.dll Not found

        Tom and Charlie:
        Here's the scenario.. I was playing around with A4.exe [in Selwyn's ver 7.01 patch download] and, when clicked, the error was displayed and alpha did not load.

        I've since discovered that starting V7 with the alpha_start1.bat, which I edited to call alpha_start2.bat, replacing the variable %1,%2,%3. etc with actual db-to-open and app name, it all seemingly works fine. I did not specifically test the blinking field issue.

        I suspect that a4.exe is hard coded to the default install path and will only work if that path is left unaltered. I installed the program to C:A4V7 overriding the install suggestion for path.

        Can't figure why THEY did't just 'call' that second batch with the first. Apparently that is what the A4.exe is supposed to do.

        Just some observations. Any further thoughts from you guys?

        Ken

        Comment


          #5
          RE: MSVBVM60.dll Not found

          Ken,

          Only thought here is that perhaps it would be advisable to get more information on what A4.exe does and does not do before modifying the start up routines as you describe. The error message suggests to me that there's a pathing issue in your modified setup. -- tom

          Comment


            #6
            RE: MSVBVM60.dll Not found

            Tom:

            Played with it some more.....I failed to note that I've run a search for the subject dll and don't have it in my system. Charlie's, is the wrong one [or perhaps he named it wrong somehow].

            Mind you , I'm not complaining just investigating. The path issue I believe must be in the A4.exe as the paths that I edited into the Start2 bat work without incident. Still don't know what loads the DLL file especially when I can't find it on my system anyway. ENIGMA?

            Say, by the way, V7 DOES seem to be 'snappier' doesn't it? Maybe my imaginiation.

            Very insteresting Like they used to say on Laugh In.

            Ken

            Comment


              #7
              RE: MSVBVM60.dll Not found

              Ken,

              I think the missing dll is used by the installer. It's a version of the visual basic runtime engine (I think)... The fact that it's now missing is probably inconsequential.

              -- tom

              Comment


                #8
                RE: MSVBVM60.dll Not found

                Tom:

                We wonder why we just don't pick up the phone and call each other.

                Look what I foun about tbe dll at...
                http://www.antivirus.com/vinfo/virusencyclo/default5.asp?
                VName=WORM_NAKED.A

                Whew, can this be a monster or what?

                Ken

                Comment


                  #9
                  RE: MSVBVM60.dll Not found

                  The a4.exe program in the Alpha Four V7.01 patch (as well as all new versions of Alpha Four V7 sold after a certain date) requires the presence of certain system DLL files on your computer.

                  The majority of newer machines already have these DLL files installed.

                  If you get an error message when trying to run A4.exe, then your machine is missing these DLL files.

                  You can download a program from our Web site that will install the missing DLL files.

                  The URL for this download is:

                  http://www.alphasoftware.com/ftp/alpha_four/V7/install_vb_runtime.exe

                  Comment


                    #10
                    RE: MSVBVM60.dll Not found

                    Ken-

                    MSVBVM60.DLL is a standard Visual Basic 6.0 Runtime file needed by all Visual Basic 6.0 programs to run.

                    There is no relationship between this DLL and a virus.

                    -Brenden

                    Brenden Cobb
                    Alpha Software

                    Comment


                      #11
                      RE: MSVBVM60.dll Not found

                      Selwyn and Brandon:

                      Thank you both - I'm downloading as we speak.

                      H A P P Y N E W Y E A R to ALL

                      Ken

                      Comment


                        #12
                        RE: MSVBVM60.dll Not found

                        More....

                        We need to share this information to all to clear up possible misconceptions. What I found was that the MSVBM60.DLL is one file, among several others, that the Virus corrupts. What happened in my case is that I probably had the files, placed in the system by the default installation routine of Windows 98 [ver 4.10.1998]. My system WAS invaded by the Virus; Norton A-V found several infected files; and was unable to 'repair' these. They were either deleted or disabled by Norton. The downloaded replacements are, indeed back in the system and all performs as advertised - EVEN the blinking fields [full screen - not windowed, as before].

                        The point in all of this is to clear up the fact that ONLY the AUTHOR of the VIRUS is to blame for this whole problem. We're grateful as always for the help from Alpha and for the download solution.

                        ALPHA ON.... Everyone

                        Ken

                        Comment


                          #13
                          RE: MSVBVM60.dll Not found

                          To all,

                          I believe several of the VB files also have to be registered after they are copied to the proper folders. It may be a good thing if alpha sent them in an install program.

                          Dave

                          Comment

                          Working...
                          X