KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q127068: FoxPro Advisor Magazine Articles May 1994

Article: Q127068
Product(s): Microsoft FoxPro
Version(s): 2.60a
Operating System(s): 
Keyword(s): 
Last Modified: 11-AUG-1999

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft FoxPro for Windows, versions 2.5x, 2.6, 2.6a 
- Microsoft FoxPro for MS-DOS, versions 2.0, 2.5x, 2.6, 2.6a 
- Microsoft FoxPro for Macintosh, versions 2.5x, 2.6a 
-------------------------------------------------------------------------------

NOTE: The "FoxPro Advisor" is published by Data Based Solutions, Inc., a
publisher independent of Microsoft; we make no warranty or endorsement,
implied or otherwise, regarding the accuracy or reliability of information
published in the "FoxPro Advisor." Please contact Data Based Solutions if
you have questions or want to order the "FoxPro Advisor."

SUMMARY
=======

Below is the table of contents of the July 1994 FoxPro Advisor, a magazine
published by Data Based Solutions, Inc., 4010 Morena Blvd., Suite 200, San
Diego, CA 92117. For more information, please call Data Based Solutions at
619-483-6400, or to place an order, please call them at 800-336-6060.

MORE INFORMATION
================

Editor's View, page 6. User vs. Developer. What is the difference between a
FoxPro user and a FoxPro developer? By John L. Hawkins.

Developer View, page 8. A Refreshing Look at Screen Displays. By Alan Schwartz.
Screen redraw speed. READ SHOW is manually triggered by executing a SHOW GETS.
Refresh experiment test screen REFR with 80 push buttons. Screen Builder, READ
WHEN, READ VALID, READ ACTIVATE, READ DEACTIVATE, READ SHOW, SHOW GET, SHOW
GETS, SHOW GETS OFF, SHOW GETS ONLY, SKIP, SCATTER MEMVAR, MOVE WINDOW,
GENSCRNX, screen blinking.

Functional FoxPro, page 14. Saving and Restoring Indexes. By Malcolm C. Rubel. An
index is easy to create, but is it easy to recreate after it's lost or damaged?
It is if you adopt the techniques in this article. IDX, CDX.

FoxPro Fundamentals, page 18. Advanced Uses of SQL Select. By Miriam Liskin.
Finding duplicate records, grouping, summary statistics, SELECT, COUNT, SUM,
AVG, MAX, MIN, BETWEEN, GROUP BY, HAVING.

Developer Toolbox, page 22. Recycling Deleted Records. By Bill Lawder. APPEND
BLANK is one of the oldest and most widely used FoxPro commands, but in most
situations, you shouldn't use it! The technique in this article is a smarter way
to add records. INSERT INTO, GATHER, and REPLACE are, in some ways, inefficient.
SET DELETED, PACK, RECALL, RAT, IIF, SET ORDER TO TAG.

FoxPro Tip, page 28. TRANSFORM()- Expressions with Style. By John D. Hosier. What
a PICTURE clause does for fields in your screens and reports, the function
TRANSFORM() can do for your character expressions. SUBSTR()

International FoxPro, page 29. Handling Text as Data. By Peter Somers. Developing
a multi-lingual application requires translating phrases between human
languages. You can automate this task by having FoxPro help you. But handling
text as if it is data can be very challenging. This article shows you how.
Parse, Parsing text phrases, eliminating array subscripts, dealing with TEXT ...
ENDTEXT blocks, searching for the quoted phrase.

Database Management, page 34. Fast Record Counting with an Index. By Tom
Lewinson. When an index is active, how can you determine the relative record
position in the index? This article uses clever techniques, and Rushmore, to do
a variety of measurements on an indexed table. RECNO(), SET DELETED ON, tag on
DELETED().

Menu Management, page 42. Add Custom Capabilities Easily. By Mike McKelvy.
Table-driven menu customization. Two routines which allow additional programs to
be added to the menu system and be run from the menu without making any changes
to the original program.

Update, page 43. Q&A Solution from February 94 for page break in a report
does not work in FoxPro for Windows, because there is no way to determine the
current print line for comparison with the number of lines wanted.

FoxPro Tip, page 44. Using ON SHUTDOWN for Automatic Time Out. By Drew Speedie.
The ON SHUTDOWN procedure can provide a global yet graceful way to terminate an
application. This is essentially the same as using TIMEOUT in the application,
except that you shut down programmatically when you determine that termination
of a READ / BROWSE resulted from executing a TIMEOUT clause.

Q&A, page 50. FoxPro Solutions. By Steve Freides and Tamar E. Granor. SHARE,
prevent second instance, FCREATE(), FCLOSE(), FILE(), low-level file, Data
Corruption, WAIT WINDOW multi-line messages with CHR(13), Screen Builder,
PRIVATE and PUBLIC memvars, Report Writer, Report variables, Summary
Information, calculate averages by sum of one field divide by COUNT of another
field, activate a second screen and completely exit first screen.

Additional query words: FoxWin FoxDos FoxMac 2.50, 2.50a 2.50b 2.50c dba fpa

======================================================================
Keywords          :  
Technology        : kbHWMAC kbOSMAC kbAudDeveloper kbFoxproSearch kbZNotKeyword3 kbFoxPro260aMac kbFoxPro200DOS kbFoxPro260DOS kbFoxPro260aDOS kbFoxPro260 kbFoxPro260a
Version           : 2.60a

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.