Visual Fox Pro

From Wine-Wiki

Jump to: navigation, search

According to the Wikipedia this software was derived from Fox Pro

1 Wine Application Database
2 Current Status
3 Tips and Tricks
4 Links

[edit] Wine Application Database

See the application database.

http://appdb.winehq.org/appview.php?appId=296

Please consider submitting your test results for running this software under Wine.

Become a Maintainer

Please consider volunteering to be an additional Maintainer for this software.

Regularly Submitting results for installing and running on the latest version of Wine makes a big difference for others considering using Wine. By looking at how well the software runs others can be encouraged to try it themselves and together you can make progress in finding workarounds. By testing the software you will also notice when something breaks and when you make a bug report, the bugzilla team will often point it out to the person who broke it. If you are slightly more technically minded, you are able to regularly compile wine and test it before each fortnightly release then you will catch breakages before each wine release.

Who can be a Maintainer? - anyone. no programming experience required.
What is required of a Maintainer? - not much, but you do make a real difference.

A big advantage of being a maintainer is that as you quickly become familiar with installing and using wine with your software, you can have a direct hand in improving wine and your software. Many times you will find very handy tips posted by others and by posting a summary many benefit from your work. When you are asked a question you don't know, simply post in the wine-users forum and perhaps someone can help.

Just by being there, you make a difference. A maintainer quickly tests each monthly release of wine, and adds to the application database a rating of how good it runs.. gold/silver/bronze or garbage. Wine is constantly being improved, and occasionally something breaks. When you do spot a breakage, file a bug in bugzilla and if you want to try and fix it you can then post to the wine-devel mailing list for advice. However, if you have a little spare time (usually about 2 hours, in between doing other things) regression testing allows you to identify which patch caused the break. By filling out a bugzilla report, posting the name of the software, and the patch which broke it to the wine-devel mailing list, the developer who broke it can have a look at fixing it.

This often results in very quick fixes.

[edit] Current Status

These are drawn from the Mailing Lists. If you are a maintainer, please add relevant information to the appdb.

[Dec 05] D. Clark: I just tested a VFP 7 app with a CVS version of Wine from about Nov 6. It seems to work okay wine archive

[edit] Tips and Tricks

These are drawn from the Mailing Lists. If you are a maintainer, please add relevant information to the appdb.

[Feb 07 Wine user]

 Fatal error: Exception code=C0000005 @12/10/07 05:09:42PM. Error log
 file C:\Windows\System32\fp7rerr.log. Called from - tmgappobj.init line
 45 (c:\program files\common\libs\appobj.vct c:\program
 files\common\libs\appobj.vct) Called from - tmgmain line 301 {C:\Program
 Files\The Master Genealogist\tmg\programs\tmgmain.prg c:\program
 files\the master genealogist\tmg.exe}

M. Reed: c0000005 is a very common error with that version of FoxPro. Looks like it uses VFP7 runtime, which is 2 versions and several years out of date. Version 7 was fairly buggy, and prone to c0000005 errors. When I see these happen in older version, I tell the client to upgrade to VFP9. It's also possible that Wine is contributing to this as well. Also, corruption tables/indexes/files can cause this. About the only thing you can do is delete and reinstall, but I'm doubtfull that will help. The next thing is to go back to the vendor and see if they have a current version based on VFP8 or 9, or if the source code is available. I have, over the years, wasted way too much time trying to fix c05 errors, and it's almost always been caused by bugs in VFP. The current version has several of these fixed because I was able to show Microsoft how to duplicate them. If you have the expertise, you can install VFP9 runtime, and make a program in VFP9 that calls the VFP7 program (tmg.exe). This forces it to run with VFP9 runtime and in some cases that fixes things. I used to run Visual AccountMate (VAM) version 5 with VFP8 runtime, and it fixed several things that were known bugs in VFP5. Unfortunately, there are a few changes to VFP9 that might cause other problems, such as the ENGINEBEHAVIOR setting that has to do with whether or not sloppy SQL will execute. VFP9 defaults to much stricter syntax and this prevents VFP7 or 8 apps running out of the box with VFP9 runtime. IOW, YMMV.

[Dec 05] D. Clark noted an important change [Dec 05]: Wine recently changed from using system to system32 as the default directory for DLLs.[...] If there is no Wine version of a DLL, then Wine will automatically look for a native version. No override is necessary. In general, you should first try running the app with no overrides, and only add overrides if necessary for a specific app. About the only exception to that would be msvcrt.dll, where you are generally better off with a native version (though there has been quite a bit of work on this one lately

[Dec 05] If you're trying to create a script or launcher to run it I have always just used:

cd /path/to/app/top/level && wine app.exe wine archive

A user was want to run a Visual Fox Pro 6 application: [Dec 05] the APP seems to work fairly well on a [debian] install of wine 0.9.1, with no crashes IF:

I put the following native dll's into ~/drive_c/windows/system32
Oleacc.dll, gdi32.dll, user32.dll
The latter two are according to the documentation a very bad idea as they access the windows kernel directly, but failing to have them there results in the app not starting and VFP complaining that it can't load them.
I must start the app from its install directory thus:
[App Install Directory prompt]$ wine [app].exe
attempts to start from somewhere else, eg:
~/$ wine "C:\Program Files\[app directory]\app.exe" result in the executable being found, but on startup it looks in the folder from which I ran the command for all dependent resources. The same thing happens if I try to use the desktop launcher links which the application installer placed on my desktop and wine menus (app looks in my home directory). Using the winefile explorer and clicking on the app works fine. my experience is that the empty windowswait boxes and the truncated tooltips still exist. I'm sure it wouldn't be too hard to fix the file manually or write a new patch based on his old one. I might look into it if I have more time. [He then mentioned] seeing ugly black boxes around radio buttons, and broken listbox graphics if the text is longer than the available space.

Another user did not report seing the same issues. wine archive

M. Winhard:[dec 05] I tried running a Vfp9 app on Kanotix 2005-3 and WINE 0.9 successfully using the default WINE configuration and the mentioned msttcorefonts. It worked using the Live-CD as well as installed on my hard disk. However the WAIT WINDOWs and ToolTips don't work properly. There is a patch for this bug but it breaks some MS installer functionality and if you switch tasks sometimes the ToolTip stays on top. If you really need this fixed the only chance is to get WINE source, apply the patch and compile it yourself. wine archive