Table of Contents for FoxPro Advisor Magazine for July 1996

Last reviewed: June 3, 1996
Article ID: Q151830
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, versions 3.0, 3.0b
  • Microsoft FoxPro for Macintosh, versions 2.50b, 2.50c, 2.60a
  • Microsoft FoxPro for MS-DOS, versions 2.0, 2.5, 2.5a, 2.5b, 2.6, 2.6a
  • Microsoft FoxPro for UNIX, version 2.6
  • Microsoft FoxPro for Windows, versions 2.5, 2.5a, 2.5b, 2.6, 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 for the July 1996, Vol.4 No.7, FoxPro Advisor, a magazine published by Data Based Solutions, Inc., Customer Service Department, 4010 Morena Blvd., P.O. Box 17902, San Diego, CA 92177. For more information, please call Data Based Solutions at 619-483-6400, or to place an order, please call them at 800-336-6060. You may also contact them by Fax at (619)483-9851; CompuServe 70007,1614; Internet 70007.1614@compuserve.com, or visit their web site http://www.advisor.com.

MORE INFORMATION

FoxPro News, page 6. Jazz Up Your VFP Apps with Class Libraries. R&R Report Writer Available in 32-Bit Version. Third-Party Tool Has Data Import and Export Capabilities. T-BASE Offers Image-Manipulation Features. Distribute and Install Applications via the Web Using NET-Install.

Editor's View, page 8. By Tamar E. Granor, Editor. A Move to the Internet. Microsoft support has left CompuServe. What effect will this have on you?. Keypoint: Discussion of Microsoft s "newsgroups" not the same as Usenet. Limitation of no persistent storage for associated user file libraries.

COLUMNS: Tips, Tricks, & Traps, page 12. By Drew Speedie. Readers provide techniques for auto-filling a text box (a la Quicken), making InputMasks work better, changing menu prompts on the fly, and much more.

Tip of the Month: Visual FoxPro 3.0. Add Auto-Fill To Text Boxes, Combo Boxes.

Tip: Visual FoxPro 3.0. Project Information Files Tab.

Tip: FoxPro 2.x., Visual FoxPro 3.0. Quickly Filter Large Tables, Allow Selective Edit.

Tip: FoxPro 2.x., Visual FoxPro 3.0. Conditional Menu Prompt Text.

Tip: FoxPro 2.x., Visual FoxPro 3.0. DOW() Can Return 0.

Tip: Visual FoxPro 3.0. Create Your Own Dynamic InputMask.

Tip: Visual FoxPro 3.0. DELETE-SQL Warning.

Tip: FoxPro 2.x., Visual FoxPro 3.0. Handy Uses for #IF .. #ENDIF.

Tip: Visual FoxPro 3.0. Beware Auto-Append into Empty Tables and Empty Views.

Tip: Visual FoxPro 3.0. Disable Timers During Debugging.

Tip: Visual FoxPro 3.0. Clean Up Unknown Data Sessions.

Tip: Visual FoxPro 3.0. Swap Buffer Modes for Easy Pessimistic Adds.

Tip: Visual FoxPro 3.0. Add A Field InputMask Property to Your Data Dictionary.

FoxPro Fundamentals. Handle Data Validation Yourself, page 18. Visual FoxPro 3.0. By Miriam Liskin. Take control of error trapping, while providing a more user-friendly interface. Add, Edit, Save, Undo.

Functional FoxPro. Visual FoxPro Command Enhancements Make Coding Easier, page 28. Visual FoxPro 3.0. By Malcolm C. Rubel. Even commands you know well might have changed between FoxPro versions - and some of those changes make your code faster and easier to read. SEEK command, SEEK(), SELECT(YourTable), SET PROCEDURE TO.

ON THE COVER: Protect your applications! It s easy: Just include a key file that contains data about the licensed user of your application. Cal Evans shows how to make it work.

FEATURES: Managing Deployment. Prevent Bootleg Copying with a Key File, page 32. FoxPro 2.x, Visual FoxPro 3.0. By Cal Evans. A key file containing data about the licensed user of your application can help prevent bootleg copying. KEYMAKE.PRG, checksum.

Avoid Application Double Jeopardy, page 66. FoxPro 2.x for Windows. By Rich Kasten. Here s a routine that lets your application determine whether a program is already running - and keeps users from opening it again. CheckRun, CALLFN(), REGFN(), FOXTOOLS.FLL, FINDWINDOW(), SHOWWINDOW().

Database Design. Change Your Point of View for Better Design, page 48. Visual FoxPro 3.0. By Will Phelps. Parameterized views let you use the same command to run different queries - and the results can be updated. REQUERY(), A more Object-Oriented View.

Menu Design. Hidden Menu Treasures, page 46. Visual FoxPro 3.0. By Nancy Jacobsen. You can include just what you want in your development and application menus. SYS(2013), DEFINE BAR, Tool Options, Edit Options, Data Options, Custom Browse Menu, The FoxPro System Menu, _MSYSMENU.

Development Tools. Better Form Templates, page 58. Visual FoxPro 3.0. By Doug Clutter. Create useful form templates that speed up development, and give your applications a standardized look and feel. Save As Class, CREATFORM Wizard, The GetClass form.

New Product. Steroids for the Visual FoxPro Editor, page 70. COB Editor Extensions. By John Hosier. COB Editor Extensions make working with the FoxPro editor easier. CEE3.EXE, VFPSTART.

ASK ADVISOR: Q&A, page 82. By Tamar E. Granor and Ted Roche. Tamar and Ted take on unique Ids, copying columns from an array, and FoxPro s tenacious search for a resource file. FoxPro 2.x, Visual FoxPro 3.x. Multi-User application duplicate records. FoxPro 2.x, Visual FoxPro 3.x. Copy column from multi-dimensional array into a different array. ACOLCOPY() vs. ACOPY(). FoxPro 2.x, Visual FoxPro 3.x. Resource file named with SYS(2005) even after SET RESOURCE OFF. SET RESOURCE TO.


Additional reference words: 3.00 3.00b VFoxWin FoxWin FoxMac FoxDos FoxUnix
2.50 2.50a 2.50b 2.50c 2.60 2.60a 3.00a dba fpa
KBCategory: kbref
KBSubcategory: FxotherReference
categories



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.

Last reviewed: June 3, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.