Articles
Search: 

Setup Wizard
Monday, January 1st, 2001
James Weil
I have ten years experience programming with VFP in a variety of environments. I specialize in n-tier application development with the Mere Mortals framework. I am also intimate with the Codebook framework.
According to Microsoft, the Visual Foxpro setup can be run in quiet mode.

RUN setup.exe /Q

This will launch and run setup without user intervention. The following parameters will run Setup in quiet mode with various options:

/Q will run setup with the "Initializing setup..." dialogue box, the progress bar, and the "Setup complete" dialogue box with the OK button at the end of the process.
/QT will run setup without any dialogue boxes.
/QNT will run setup with the "Initializing setup..." dialogue box only.

If you create a Netsetup installation on your server, the first time Setup is run, the setup.exe will create a Setup.stf file in the setup folder in the user's application directory. The second line of this file is datetime stamp, which can be compared to the datetime stamp in the setup.stf file on server. The tenth line of the user's setup.stf file contains the UNC path to where the setup.exe on ther server resides.

If an application is recompiled and the Setup Wizard is re-run, you can have your application open the two files before READ EVENTS is issued, compare the date stamps, display a dialogue box that a new version is available, and run the setup from the server in quiet mode.

After the run command is issued, I return false. My application exists, but the Foxpro Setup continues on its merry way until completion. At that point the user knows enough to re-run the application. The setup.exe copies a fresh version of the setup.inf file to the user's hard drive, keeping everything in synch. Works like a charm each and every time! I hope this benefits the community.

See article Q194572 for more info about running the Foxpro Setup in Quiet mode.

More articles from this author
Friday, September 21st, 2001, by James Weil
This article is an excerpt from the Mere Mortals framework Developer's User Guide, written by Kevin McNeish. The default memory buffer size that Windows assigns to Visual FoxPro at startup is often incorrect. Usually, Windows reports more physical memory than is truly available. This means that Visual FoxPro is often using Virtual Memory (on the hard disk) when it reaches the high end of its memory pool. This can slow Visual FoxPro down considerably! To get around this problem, you can use...
Sunday, July 1st, 2001, by James Weil
The long-awaited release of version 6.1 of the Mere Mortals framework from Oak Leaf Enterprises Solution Design, Inc. provides a quantum leap from a logical three-tier architecture to a true Windows’ Distributed Network Architecture (DNA). Although this was Flash's original vision for its Codebook 3.0 framework, the Mere Mortals implementation is a radical departure from the original Codebook paradigm. A Bit of History In the beginning, there was VFP 3.0, and a myriad of 2.6 programmer...