Does anyone know of a compatibility problem with Windows 95 and FoxPro
2.5 for dos. We upgraded our IS computers about 6 months ago. Since
then we have had some very strange things happen to our databases.
**WHAT? WHAT?**Quote:>Does anyone know of a compatibility problem with Windows 95 and FoxPro
>2.5 for dos. We upgraded our IS computers about 6 months ago. Since
>then we have had some very strange things happen to our databases.
I run FPD26 under W95, but have had no real problems as yet.....
Middleton Maintenance Group PLC
Birmingham, England. Tel:(44)121-326-7777
On Fri, 23 Jan 1998 11:52:48, Chris Weston
> **WHAT? WHAT?**
> Really, what do you call "strange"?
> I run FPD26 under W95, but have had no real problems as yet.....
Michael MotekQuote:> --
> Chris Weston
> Computer Programmer
> Middleton Maintenance Group PLC
> Birmingham, England. Tel:(44)121-326-7777
When we append records into a table, modify some of those
records, and then close the table, sometimes some of the
data appear to be "shifted" to the left by 64 or 128 bytes.
MS Tech support suggested turning off all caching on our
network, changing our network client, and checking the
versions of our drivers. When these failed (and we really
didn't want to run our network without caching), we put in
a temporary solution for all affected programs--close and
reopen each DBF after each APPEND FROM. This seems to be
averting the problem, but we'd be very very interested to
hear of any other possible solutions.
Is this what you were after?
Mind you, moose bites can be pretty *...
I have the sorry task of moving a client from Lantastic to Windows
The client's core application is a FoxPro 2.5 based
accounting/inventory/sales entry system that has been running under
a Lantastic peer-to-peer network (the application file server is also
a user's workstation).
The client is moving to a Windows 95 accounting application to replace
the curretn FoxPro app, but will need to run the FoxPro app for a
period of 2 to 6 months on a Windows 95 peer-to-peer network.
I have installed a new 350MHz PII 32M RAM Windows 95 ORS2C machine
as the new server/workstation and converted all other Lantastic/DOS
workstations to either Windows 95 or Windows 3.11 (Old 486 monochrom
systems running in DOS only mode with "net start full" in AUTOEXEC.BAT
to start the Windows networking and mount the shared application
directory as drive F:)
Here's the problem: The application developer insists that they have
Windows 95 peer-to-peer running in his office with a combined
server/workstation machine and the app runs without problems.
However, at the client's office, the application runs fine until
we try to run the application from the server/workstation machine.
The application will start and run ok for anywhere from 5 minutes to
3 hours but then it will lockup and "control-Alt-Delete" brings up the
task window that reports "application not responding."
The application directory is sharred to the network and mounted as
drive F: on the workstations. The application lives in c:\arplus
on the server/workstation and starts up in c:\arplus. The FoxPro 2.5
runtime and application programs and data files are all in c:\arplus.
Are there any Microsoft Patches for Windows 95 that I need to apply to
Can anyone recommed configuration file settings for the
server/workstation to avoid conflicts between running the application
localy on the server/workstation and users running in the mapped network
The client ran the application without trouble for an entire 8-hour day
by avoiding running the applicaton from the server/workstation console.
But since the new server/workstation is the fastest machine in the
office, they don't want to abandon it as a workstation.
S.M. Fabac & Associates