By Marcia Akins, Andy Kramek, Rick Schummer, John Hosier

In case you are going to exploit VFP for greater than informal GUI adjustments for your application, this ebook is a wealth of information. Concise, in-depth, and a stunning addition on your assortment.

Show description

Read or Download 1001 Things You Always Wanted to Know About Visual FoxPro PDF

Similar software: office software books

CIO Survival Guide: The Roles and Responsibilities of the Chief Information Officer

CIO Survival consultant is a management handbook for the rising function of the manager info Officer. This publication helps and courses CIOs in buying or improving their technical talents and management potential to be an entire and revered member of the administrative crew. It comprises exposition and perform of the abilities and capabilities required to be a profitable CIO.

Additional resources for 1001 Things You Always Wanted to Know About Visual FoxPro

Example text

Additionally it will be triggered if you try to exit Windows while Visual FoxPro is 28 1001 Things You Always Wanted to Know About Visual FoxPro open. ) SHUTDOWN procedure is What goes into an On Shutdown procedure? 0 was that a QUIT command would close open Modal forms and cancel any existing READ EVENTS. 0. prg' for cleaning up the development environment and the code which was used there can, with minor modifications, be used as the basis for your shut down procedure. One such modification is to include a test to determine whether the currently executing program was actually called from the development or run-time environments.

How can I ensure SET commands apply to a private data session? ' Normally you will be using data sessions that are being created by a form (or formset) as 'Private'. It also matters whether you are using the Form's native DataEnvironment or not. INIT() DATASESSION: 2 ALIAS(): Notice that the DataSession is always 2, the new Private DataSession, and that the table is already available in that DataSession when the form Load() event fires. The anomaly that OpenTables() occurs before BeforeOpenTables() is more apparent than real and is occasioned by the fact that the BeforeOpenTables() event is actually triggered by the OpenTables() method.

Resize() event is fired after the toolbar's BeforeDock() event but before the AfterDock() event. Actually the event tracker indicates that the Resize event fires twice! (Presumably this is so that the screen resizes when the toolbar is moved from the main screen area to the title bar, and again after it is actually docked). T. F. Resize() event at all! Although the screen actually does re-size when a toolbar is undocked, the new size is not available to any method that can be called from within the toolbar.

Download PDF sample

Rated 4.82 of 5 – based on 22 votes