FastTips for FoxPro for Windows: Using FoxPro for WindowsID: Q96175
|
======================================================================
Microsoft(R) Technical Support Application Note (Text File)
FW0934: USING FOXPRO FOR WINDOWS QUESTIONS AND ANSWERS
======================================================================
Revision Date: 10/93
No Disk Included
The following information applies to Microsoft FoxPro(R) version 2.5
for Windows(TM).
----------------------------------------------------------------------
| INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY |
| ACCOMPANY THIS DOCUMENT (collectively referred to as an Application |
| Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER |
| EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED |
| WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR |
| PURPOSE. The user assumes the entire risk as to the accuracy and |
| the use of this Application Note. This Application Note may be |
| copied and distributed subject to the following conditions: 1) All |
| text must be copied without modification and all pages must be |
| included; 2) If software is included, all files on the disk(s) |
| must be copied without modification (the MS-DOS(R) utility |
| diskcopy is appropriate for this purpose); 3) All components of |
| this Application Note must be distributed together; and 4) This |
| Application Note may not be distributed for profit. |
| |
| Copyright (C) 1993 Microsoft Corporation. All Rights Reserved. |
| Microsoft, FoxPro, and MS-DOS are registered trademarks and Windows |
| is a trademark of Microsoft Corporation. |
|---------------------------------------------------------------------|
1. Q. I occasionally experience problems when trying to open more
than 15 database files at one time. What could be wrong?
A. Oftentimes, this problem can occur if the MS-DOS SHARE command
is not used correctly in the AUTOEXEC.BAT file. Make sure you
have the correct SHARE command in your AUTOEXEC.BAT file. For
example:
share /f:4096 /l:500
2. Q. I'm running Windows for Workgroups. Do I need to load Share?
A. No. Windows for Workgroups automatically loads and uses a
program called VShare, which takes the place of Share.
3. Q. Where does FoxPro store its temporary files?
A. FoxPro for Windows stores its temporary files in the same
directory that Windows uses to store its temporary files,
unless you specifically designate an alternative location by
including one or more of the EDITWORK, SORTWORK, PROGWORK,
and/or TMPFILES statements in the CONFIG.FPW file. The location
of Windows .TMP files is specified with the MS-DOS environment
variable TEMP. In most cases, you should let FoxPro .TMP files
reside in the same location. However, if this location is a RAM
drive, make sure that there is enough space available for both
FoxPro and Windows .TMP files.
4. Q. I used to use the RUN command to change drives and directories
in an application when I used FoxPro for MS-DOS. However, this
isn't working in FoxPro for Windows. Why is this?
A. Each time you issue the RUN command to change drives and
directories, Windows opens a new "session" of MS-DOS (otherwise
known as a "virtual machine") and executes the command within
the newly created session. When you exit from this session, or
"shut down" the virtual machine, you are returned to the same
drive and directory where you started. Because of this
behavior, you should take advantage of FoxPro's own drive and
directory commands to change drives and directories instead of
using the RUN command. (For example, the SET DEFAULT TO
C:\<NEWDIR>command actually issues the MS-DOS CHDIR command.)
5. Q. Why isn't FoxPro registered in REG.DAT within Windows?
A. Only OLE servers are registered in REG.DAT. FoxPro is not an
OLE server.
6. Q. Why doesn't the value returned by SYS(2010) match the number
specified by the FILES setting in the CONFIG.SYS file?
A. Windows interacts with the MS-DOS open file tables in such a
way that the value reported in the MS-DOS box and in Windows
may be different.
7. Q. FoxPro for Windows automatically displays a status bar located
at the bottom of the main window. Is it possible to remove this
status bar? Is the MS-DOS-style status bar available?
A. The Windows-style status bar provides the same information as
the MS-DOS-style status bar, plus it can also display
information about the currently selected menu name or command
and messages created in commands. It can even display the
system clock.
The Windows-style status bar is displayed by default. To remove
the status bar, either issue the following command in the
Command window
set status bar off
or enter the following command in the CONFIG.FPW file:
status bar = off
To restore the status bar, simply substitute ON for OFF in the
previous two commands.
When the Windows-style status bar is active, messages created
in commands such as DEFINE MENU, DEFINE POPUP, DEFINE BAR, @
... PROMPT, and so on always appear in the Windows-style status
bar.
NOTE: When the Windows-style status bar is active, the SET
MESSAGE TO command used to specify a message location is
ignored.
When the Windows-style status bar is active, you can display
the clock on the right side of the Windows-style status bar
either by issuing the following command in the Command window
set clock status
or by entering the following command in the CONFIG.FPW file:
clock = status
For reverse-compatibility with existing FoxPro 2.0
applications, FoxPro for Windows displays the character-style
status bar when the SET STATUS ON command is issued.
8. Q. When I issue the SET DISPLAY TO VGA50 command and then issue
the SET DISPLAY TO VGA25 command to restore the previous
setting, the status bar disappears. How do I restore the status
bar?
A. Issue the SET STATUS BAR ON command to bring the status bar
back.
9. Q. When I issue the ? SET("DEFAULT") command in the Command
window, shouldn't I get a full path display rather than just
the drive letter?
A. No. This behavior is consistent with FoxPro 2.0 for MS-DOS. Additional query words: FoxWin 2.50 ivrfax fasttips
Keywords : FxinteropOle
Version : 2.50
Platform : WINDOWS
Issue type : Last Reviewed: August 3, 1999