Re: VFP Updates?



Hi Linn,

I, as you, am not a full time VFP developer and maybe even further
behind than yourself. Reading the article Dan pointed you toward
enforced that belief. It seems there are at least a dozen major
considerations for installing and running a VFP app in Vista.

However, I think there's a saving grace: If you don't need to register
components or DLL's, and your users can tolerate the "annoyance" of
another root directory (most of my users don't even know what a root
directory/folder IS), and you don't need to write to registry, I think
you could put the app and the data in shared folder(s) and not have to
deal with XP/Vista differences.

Note: I've used config files, .mem files and memo fields to hold user
settings in various apps. I think that is more reliable than writing
them to the registry. They can be part of the user's normal backup and
can be easily reloaded if the user has to reformat or wants to reload
the app on another computer while saving his/her settings.
Registry--that's a different story for the average user.

Anyway, that's my 2c.

Steve


On Thu, 14 May 2009 09:34:55 -0500, "Linn Kubler"
<lkubler@xxxxxxxxxxxxxxxxxx> wrote:

Hi,

I just realized how far behind I had fallen. I don't do development as a
full-time job, I do it quite sparatically. That said I realize that I'm
still running VFP 9.0 sp1 and developing specifically for XP. However I
soon will need to support Vista so I'm wondering what I need to do
differently, if anything, in my applications to allow them to function in
Vista? I see there is a service pack 2 available and something called
Sedna, not sure what that's all about. Can anyone fill me in?

Thanks in advance,
Linn

.



Relevant Pages

  • RE: Windows XP and VFP 8.0
    ... This error message is not a VFP error. ... Have you contacted the developer to ask him what might prompt this error? ... >The app is served in a shared folver by a Win98 pc. ... Clients are WinXP, ...
    (microsoft.public.fox.helpwanted)
  • Re: How to programatically check for and register OCX
    ... I'm sure you can search through the registry but I found an easier way to ... check if it is registered (only if you have VFP 8) ... > I have an app I'm going to be deploying to about 50 users. ...
    (microsoft.public.fox.programmer.exchange)
  • Start/Run uses existing VFP session
    ... When I Start/Run a VFP 6 .APP, if I have VFP 6 open, it uses the ... Is there a registry or other setting to have it ...
    (microsoft.public.fox.programmer.exchange)
  • Re: The curse of constant fields
    ... production branch, EAR construction etc) for a reasonably important J2EE app I am pretty fanatic about sanitizing everything prior to an official build. ... our environment it would be unrealistic. ... Because a lot of time can be wasted if a tester reports that an error is still there, and then it's a question of is the error still there because the build is flawed, or because the developer who "fixed" it only fixed it for a different use case or in his own development environment. ...
    (comp.lang.java.programmer)
  • Re: Foxpro now an "A" language
    ... VFP -- it so much easier it's silly. ... instance that app that I'm still supporting in VFP was done in VFP 8.0, ... designing a large app in C# ... A lot of people *say* they're replacing VFP apps. ...
    (microsoft.public.fox.programmer.exchange)

Loading