One of the benefits of VFP is that you might be able to run the application from a central server. Nothing to be installed on the workstation itself? Might be worth testing.
Another approach is to have the workstations run a "stub" that creates a directory on the workstation and copies the VFP runtimes, and EXE locally with enough to get it running. Tonight the workstation is wiped. Tomorrow that same stub is run and the VFP app is copied locally again. Again, might be worth testing out. Nowadays, the VFP runtime files are tiny compared to the .NET runtimes! :O :D Good luck. -----Original Message----- From: ProFox [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, August 11, 2017 10:02 PM To: ProFox Email List Subject: RE: VFP9SP2 apps on Citrix On 2017-08-11 14:55, Kevin J Cully wrote: > We used Citrix at a healthcare company I worked at around 2005. > Basically everyone came in to an office, just to telecommute into our > hosted servers that was in a city 30 minutes north of our office. It > was a valid approach to better securing workstations. > > I was doing a good bit if VFP9 at that time and there wasn't much (if > anything) that I had to do to the application. I tended to make the > buttons bigger because with the remote-aspect of running the app, the > double+clicks didn't always "take". We called it "having to > triple+click" ... or ... "click it like you mean it!" It had more to > do with Windows and the nature of following the mouse movement from > local to remote. > > They had portable profiles however. They didn't wipe the image as > there were valid reasons that people would have customized desktops > and customized software installations, even if the Windows was remote. > > This approach saved us on PC purchases as well. We could buy pretty > minimal PCs as the real horsepower was in the Citrix VM'd PCs. > > Hth, > Kevin Thanks for sharing that, Kevin. If you had to design an app for the "wipe daily" scenario, how would you do it? Personally, I think Andy Kramek's idea (years ago!) of using meta-data that had code in memo/text fields may work well for this scenario. Andy's approach may not have been good for source code control (as per one detractor), but the idea of self-updating easily was on-point, imo. [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/f82db4de49440845a14b540f6c2df6a92eea9...@blufitspmbs01.cherokeega.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
