Windows 7 compatibility issue and more

[Steve Wiltsie]

> Long-time client with relatively new fP user suddenly cannot start her
> fP application.  When starting either my app. directly or even P.EXE,
> Windows 7 issues the following error:
> 
> "This program or feature cannot start or run due to incompatibility
> with 64-bit versions of Windows"
> 
> I configured this work station for fP myself last year when it was
> replaced by their I.T. vendor (formerly an XP machine).  It has run fP
> w/o issue until today.  Client is not aware of any changes made to
this
> machine since she last used her fP application (this past Friday).
Any
> idea what may have changed or been changed to suddenly cause this?  To
> avoid possible changes made to the shortcut, I had her try starting
the
> fP app. directly from her network drive (bypassing the shortcut) and
> starting P.EXE directly, both now cause the incompatibility error.  At
> the moment I cannot confirm the version of fP since I cannot start fP,
> but know it is either v4.8 or v5.0 because I use the PFPOSTPRINT
> feature in conjunction with PrintWizard.
> 
> Don Coleman

Don and all,

I think the computers must have had too many days off with the Labor Day
holiday.  I have a long-time client who has been using filePro to run
their business for about 20 years.  They are currently on a Windows 2011
Small Business Server and have been using this server for most of this
year.  Today one of the main filePro functions is giving the error:

------
Microsoft Visual C++ Debug Library
Program: M:\fp\dclerk.exe
Module: M:\fp\dclerk.exe
File:

Run-time Check Failure #3 - The variable 'er' is being used without
being initialized.

The option buttons are Abort   Retry   Cancel.
--------

I have made no changes to this program for several weeks and suddenly
this shows up repeatedly today.  There is no variable 'er' in the
processing tables for this file.  I have connected to their server and
am in the file but the error is not showing up now.

Is it just a full moon or does anyone have an idea of what that error
means?

Thanks,
Steve Wiltsie
microCONCEPTS