Win 7 64bit Disguises filepro errors

[Jerry Crespi]

Hi,
This is a heads up:

I have a client who has recently moved from Win XP  to Win 7 64 
bit.  Their filepro app is a large and complex program that helps 
them do fiberglass fabrication.  It also handles invoicing, 
inventory, PO's and a host of other office functions.  They only have 
6 users and are on 5.7 with a runtime system and only one development system.

For the first time since their move, they used a part of the program 
on Win 7.  It produced errors that stated that rclerk was no longer 
working with the following error message:

Exception error 3221225477 (0xc0000005) in process failed 0(0x00000000)
comspec="Y:\fp\rclerk fabricate -s1

So I tried the same program with dclerk and received a similar 
message.   At this point, it looks like a broken *clerk module.

I checked the programs on my system (a tried and true XP Pro box) and 
it worked flawlessly.  So it looked like they could have had memory 
issues, *clerk issues, viruses, etc.
As you all most likely do, I gave them steps to take including 
unloading memory hog programs, rebooting etc.  No luck. Same errors.

Then at night after they closed, I logged in remotely and ran the 
program. Same errors.  Thanks to the wonders of double monitors, I 
then began comparing programs between mine and theirs.  (Remember 
mine worked.)   They had indexes that required rebuilding, missing 
indexes, and a slightly older input processing table.

There were no filepro errors that lookups had failed, or an index was 
missing, or anything.  Just the windows exception errors.

The moral of the story? Don't believe what you see or anything that 
anyone tells you.

Windows 7 64bit may not report 32 bit program errors correctly.



Jerry Crespi, Ph.D.
President
Allied Business Systems Inc.
V. (714) 963-5554
F. (714) 964-0061  


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4158 / Virus Database: 3629/6837 - Release Date: 11/14/13
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20131115/49a19e50/attachment.html