to order online
Subscription info here.
to order online.
Tamar E. Granor,
Length: 24 pages (A4)
Formats Available: Printed (incl. electronic) or Electronic only
Printed format: A4 (210x297 mm or 8.3x11.7 in)
Electronic format: PDF
Single Issue Price ($US): 29.00 (printed+electronic) $19.00 (electronic only)
Press date: September, 2012
Printed issue availability: 2012/09 issue being mailed in September, 2012.
Electronic issue availability: Available for download.
Source code: Available for download.
September, 2012 - Number 28
The Business Case for Upgrading Apps to Visual FoxPro in 2013
So 2013 is getting ready to stare us in the face, and it seems every week we're getting calls from customers who have FoxPro 1.x, 2.x or Visual FoxPro applications in production, wondering what to do with them. These customers have thousands, perhaps tens of thousands of hours invested in their applications, systems that in some cases run their entire company, but they're looking at potential problems as Windows goes through its 5th or 6th new release since their application was initially written.
This article argues that since 2011, the business case for upgrading these Fox apps to VFP - instead of doing a complete rewrite in a different language - has actually become stronger. It will come as no surprise to you, gentle reader, that this viewpoint is anathema in many circles. Naysaysers will bring up many specious arguments about why continuing to use VFP is a bad idea. In this article, I'll first debunk those myths. Then I'll provide some solid reasons that make many types of upgrading a compelling proposition. Finally, I'll deliver the knockout punch that might even have you reaching for the “Uninstall .NET tutorial” button in your Control Panel app.
Using Assign methods
[[Tamar E Granor]]
Assign methods let you take action when a property changes.
In my last article, I introduced Access and Assign methods and showed some examples of Access methods. This time, I’ll explore Assign methods, which fire when the corresponding property changes, essentially giving you a "property changed“ event.
Creating ActiveX Controls for VFP using.NET, Part 3
Doug continues his series on creating ActiveX controls using .Net by adding additional classes to the library of controls he’s been building.
VFPX: Data Explorer
The release of Visual FoxPro 9 introduced a new Xbase tool called the Data Explorer. Microsoft released a new version in the Sedna release to correct the known bugs and introduce a handful of new features. This article explores some of the newest features added to the Data Explorer past the Sedna release and released on VFPX in a project known as Data Explorer 3.
OS Based Invisible Data Compression in VFP
Data compression with external zipping utilities in VFP applications has been featured in more than one article in this forum over the past quarter century. XP onward, Windows has offered OS managed, behind the scene compression of data in folders and files via a single FILE_ATTRIBUTE control bit. Now long stagnant, VFP even from its inception offered scant choices for system level control of anything, save for a few isolated SYS function settings.
Controlling OS handled compression directly from within VFP was taken on as an R&D challenge. This initiative has led to the creation of a new function SETCOMPATT (Set Compression Attribute) in the existing VFP booster library Foxparse, a C based API. OS based, black-box data compression is a device driver functionality which can now be turned on or off directly from a VFP application. Decompression is implicit and automatic, on data access. The user only needs to call SETCOMPATT once to set the compression status of the target folder or file. This technique, unfortunately, is dependent on the device driver being compression enabled, limiting its universal use. Foxparse.fll in this download is the most current release of this library to date.