Microsoft visual foxpro has stopped working

This program has worked before on the same computer. How do I get the program to open? This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. Does this mean anything? Could it be that these files already exist on my machine in some other location?

Had I known the file names to be extracted, I would have done a search without bothering about this. This is why you must always either install "as administrator" or the installer asks for permission to elevate to administrator level. The files don't need to be installed there, and indeed the best place is where the application is installed. But this installer registers this version of the runtime for every VFP9 SP2 application and in such a case that folder will be created and is the default path.

So please just install there. Don't think too much about this and if you don't trust me, then why did you come here at all? Also, if you're asked with a default, that normally means you have free choice and the default is no bad idea.

Tore might have a good idea, but I don't see how insufficient write access into the program file folder would lead to your error, and as you tell the software is made for Win8 or later that would also have been a problem on Win8.

But since Vista, the OS redirects writes and reads into read-only system folders like program files to a user profile folder, but that doesn't cause it not to work.

If that still doesn't work, the only other reason I can think of is having a bad setup download. Eylon, your software was running smoothly before? Have you now reinstalled on an other pc? Did you check with the vendor under which version of VFP this software was constructed?

Are you sure the runtimes tally with the version of your software? Regards, Koen. I ran and vfp9sp2rt. To my knowledge, this should have only updated the database and not the code. Any thoughts about this? Koen- The software ran smoothly on older machines of mine running Win 7. You may start only deleting the msvcrt You may also compare the DLLs, do you see any differences? The runtimes I tampered with were: msvcr Could not load resources.

File Comparison: 1. Size is the same. Koen- I shared with you the installation file from my Drive. I appreciate very much the time you put in trying to help me sort out this mess.

Whether the name is upper or lower case won't matter. Then I guess it's that EXE itself, that's defect. If a new download of the software setup doesn't work, I wonder if Koen will get the same error. If not, the only other vector left over is OCXes, but I don't remember missing OCX registrations to cause such a fatal error, in the worst case you get a message you can ignore and a form runs without that control, which can cause a lot of follow up errors, but no fatal error and all-in-all nicely points out which OCX isn't registered.

It seems to search for an ActiveX component. When you HD is cleaned, than use the installer again and let it install in the default directories. The same question goes for reinstallation. Would the order of uninstall and reinstall matter at all? Otherwise there may be too many files and file types to look for and delete. Or did mean exactly that? Another issue is privileges: should reinstallation be done with elevation? Thank you Koen and Olaf once more. Right-mouse on the icon and change the compatibility to a lower version of Windows.

By 'search everything' I mean your complete HD, all directories. Tool "Everything" is a fine tool to do this. Or is it that your program errors with "Visual FoxPro 9. In that case provide me with the username an pw and indicate where and when the error occurs on your side.

Koen, it's not really a good idea to just delete the files vfp9sp2rt. Such actions cause more problems than they solve. It's true you sometimes need to go the cumbersome route, but as long as the software has a good entry in the system and an uninstaller, that should at least be able to remove all necessary stuff from the registry, too.

Otherwise you'll need to advise to go through the registry, too. I'd use available uninstallers first, that means pick the software from the list of installed programs for uninstallation and after that delete what remains after they ran. I don't see how that can help a lot, the vfp9sp2rt. And that's quite solidly working, unless some foxpro executable has a broken vfp9r. Eylon, one last check, if you're not already in the process of uninstalling everything.

If so, look at this after reinstallations: Do you have the msvcr Don't touch those. You may look into it further using a right. I have one with Version 7. Olaf, I am sorry if I was unclear, but I said exe use windows uninstaller Of course an exe sould never be deleted by deleting but should be uninstalled, however it occurs that sometimes the uninstaller unstalls from the registry but not physicaly removes the file.

That should also be done in this case, just to avoid there remain no old files on your HD. Also ofcourse instead of removing, a renaming is more to be advised. Was planning to do that over the weekend.

I looked up msvcr Does this get us somewhere? Yes, that get's us somewhere, because likely the version you have in SysWow64, while being newer, is causing the errors. So rename the one in SysWow64 and see if that makes si.

Different versions of a DLL might have downward compatible classes and functions inside them, but at different entry point addresses, and that difference can cause a fatal error for entering a dll at the wrong addresses. The mechanism isn't that hard coded adresses, a DLL exports symbols for its entry points so two different versions are usable, but I only know for sure the older 7.

Now, there might be any other software which needs the 7. I'm almost sure the way you have it the local old version 7. That would be a threat to VFP application. I can't really imagine that. But your situation doesn't work, so it indicates that already. Could be one of the tow DLLs is defect and not just the wrong version. That would complicate things. Olaf- I renamed the two files one at a time but the software failed on both renames.

In the other directory this was not required. The end result was nevertheless the same. Tough luck. That elevation need is not odd, when you act on a system folder you need elevation, that's the major resons installers need elevation to really install something and not just put files into redirected folders or virtual registry and "seem" to work.

It was my major concern, you could try one more thing and put the 7. But I doubt it'll make a difference. I now think no matter what you do, the EXE itself, the si.

Eylon, please mail me the username and pw in order for me to check Olafs's assumption quote I now think no matter what you do, the EXE itself, the si. Thank you Olaf. Koen- Your suggestion is sensible. This trial may indicate if the fault lies within the installation file.

I will send you the data over email for better security. Have you even tried my suggestion? Eylon, nothing wrong with the software it can be installed on Win10 64bits. I think there is something 'rotten' on your pc.

Is this the only. Eylon, Koen, OK, one thing I didn't yet think of is a broken external file like the foxuser. Actually, something too often causing problems, that we shouldn't overlook that. But because I also don't have much use of it in my projects I add a config file suppressing the generation of that DBF and I often forget about its existence. Koen, you know what I mean, you don't need to read the rest, just if your getting back to this before Eylon you could simply see whether a foxuser.

A corrupt fioxuser. The reason is of course not just the generation of such a file but reading it. There is a way to configure this to not be created, but we don't yet need to get there, it would also suffice if it's regenerated because you delete a corrupted file set and the next one likely will not be broken. In the simplest case you find two files foxuser. It could also be in both when the vendor added a foxuser.

So please look in both places and delete the files in both places. But before you do that, the software might make use of it, so there is no reason to avoid it, once it is generated correctly and works there always is the risk of it becoming broken again, but it will not happen so regularly and the fix will be to delete it. What you might win keeping it is the software remembering your window position or positions, that's one of the features stored in that table. The software is installed in the 'normal' place by the setup.

The software runs like a charm. The error message "Visual FoxPro 9. The vendor did not add a foxuser. Let us wait what Eylon comment is on this situation. No, it just is the way a C error is shown in Win8 8. Friday, March 19, PM. Marked as answer by jsimps0n7 Sunday, June 27, PM.

Sunday, June 27, PM. Granor 0. Naom, Thanks for the reply. I have been in a long email exchange with IAM. They don't seem to have an answer. Try to reinstall Visual FoxPro. Please "Mark as Answer" if this post answered your question. Saturday, March 20, AM.