none
F2 key (and Enter key) crashing application RRS feed

  • Question

  • A client of ours has been running a our custom-written application since 1988. This application was originally written for to work in DOS, but later, my husband rewrote it to work in Windows. They have been using it for all these years and it has been working without issue all the way through Windows 7.

    Recently they added some new computers that are running Windows 10. They installed the application on those computers and have had an assortment of problems since.

    The F2 key, used by our application to duplicate data in any given field from that in the record previously entered, now produces a run-time error and shuts down the application.

    The Enter key, used to  move around from one field to another, does the same thing.

    It also appears that the DOS copy command is not working.

    The IT team at this client did perform some research into what might be the difference between the old machines and the new, other than Windows 7 and Windows 10, as I am running this same application in Windows 10 on my computers without issue, as are our other clients. He gave me a list of components that were present on the new and not on the old. Because our application is written in Visual Basic (5), he thought this might have something to do with the reason our application no longer behaves as it did before. Those components are as follows:

    Microsoft VC++ redistributables repacked.

    Intel Corporation

    12.0.0.0

    20170703

    2017-12-04 00:13:15

    Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.30501

    Microsoft Corporation

    12.0.30501.0

    2017-12-04 00:13:15

    Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.40649

    Microsoft Corporation

    12.0.40649.5

    2017-12-04 00:13:15

    Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.30501

    Microsoft Corporation

    12.0.30501.0

    2017-12-04 00:13:15

    Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.40649

    Microsoft Corporation

    12.0.40649.5

    2017-12-04 00:13:15

    Microsoft Visual C++ 2013 x64 Additional Runtime - 12.0.40649

    Microsoft Corporation

    12.0.40649

    20171115

    2017-12-04 00:13:15

    Microsoft Visual C++ 2013 x64 Minimum Runtime - 12.0.40649

    Microsoft Corporation

    12.0.40649

    20171115

    2017-12-04 00:13:15

    Microsoft Visual C++ 2013 x86 Additional Runtime - 12.0.40649

    Microsoft Corporation

    12.0.40649

    20171115

    2017-12-04 00:13:15

    Microsoft Visual C++ 2013 x86 Minimum Runtime - 12.0.40649

    Microsoft Corporation

    Can anyone give me some insight on this so that I can rectify the problem for this client and have some answers ready for the other clients (and my own computers) should they encounter the same things at some point?

    Thank you.

    Barb

    Wednesday, December 6, 2017 1:38 PM

All replies

  • Hi Barb,

    This forum is for VB.NET. Looks like you are using C++, if that is the case I can move your question to the C++ forum if you want me too.

    Okay I just noticed this is VB5, when creating your post there was a banner indicating this forum does not assist for classic VB so I'm moving your question to an off-topic forum.


    Please remember to mark the replies as answers if they help and unmark them if they provide no help, this will help others who are looking for solutions to the same or similar problem. Contact via my Twitter (Karen Payne) or Facebook (Karen Payne) via my MSDN profile but will not answer coding question on either.
    VB Forums - moderator
    profile for Karen Payne on Stack Exchange, a network of free, community-driven Q&A sites


    Wednesday, December 6, 2017 2:08 PM
  • Microsoft stopped supporting Classic VB (VB 6 and earlier) a number of years ago. While they still support the runtime files there is no support forum here for this version. This forum is for Visual Basic .NET, which is a bit different than Classic VB.

    You didn't mention what type of problem (specific detailed errors?) you were having with the DOS Copy command but I would suspect that it's probably a configuration, permissions or UAC issue, given that older legacy apps tend to do things that may not be allowed in newer versions of Windows. The below forums offer support for Classic VB so you may want to post there:

    http://www.vbforums.com/forumdisplay.php?1-Visual-Basic-6-and-Earlier

    http://vbcity.com/forums/26.aspx


    Paul ~~~~ Microsoft MVP (Visual Basic)

    Wednesday, December 6, 2017 2:09 PM