I'm thinking security also but the networking guy says the folders that the application uses have full rights, we'll see if this is true once I'm able to get into the server and install foxpro and yes the plan now is to migrate it to 9.

Thanks.


>It might help if there was more info on *what* isn't working.
>
>The most likely culprit is security - Modern Windows versions run under User Account Control, which is a limited rights account. Most notably if you're writing data in the installation directory (Program files, or arbitrary user folders off the root), the data is not directly accessible. UAC will re-route the folders to somewhere else and for DBF/CDX files that usually ends up with corruption. Basically the data files should live in a User or AppData folder that the user has full access to.
>
>There are other issues - and Doug Hennig's paper (mentioned in another message on this thread) outlines those. Most of the issues are not related to VFP 6 per se, but to OS changes. That said - VFP 6 is a pretty unstable version of VFP and it'd be a good idea to upgrade it. With a few environment setting changes VFP 6 code will run pretty much unchanged but will likely give a much better experience and stability on newer versions of Windows.
>
>+++ Rick ---
>
>>Hi guys,
>>
>>I got a call from a guy that has an application in foxpro 6.0 and he moved the application to a windows 2012 Server and now has all sorts of problems, the application bombs right off the bat (running the app straight from the server), I haven't started working on this (still don't have access to the source code) but I haven't used foxpro 6 in AGES, any problems running a foxpro 6.0 app in 2012? What sort of issues can I run into? should I be on the lookout for? I might also need to get a hold of a copy of 6.0 if I can't find the one that I had.
>>
>>Thanks!