Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
VFP Report Designer Bug (Again)
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire de rapports & Rapports
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Vista
Network:
Windows 2008 Server
Database:
MS SQL Server
Divers
Thread ID:
01352983
Message ID:
01353606
Vues:
12
>Dear GOD (or UT users), please help me figure out why I lose report changes 10 times a week due to this report designer bug that nobody else can reproduce. Amen.
>
>I've already posted this once, and gotten great responses, but no fix, and the bug continues to plague me, so I'm trying again:
>
>I make a bunch of changes to a report. Open another report to copy some code and then try to save the report and BAM "file not open" error pops up and the only way to get out is to End Task... Lose All Your Work... Goodbye... Have a Nice Day.... #($*#$#$%# YOU VFP9SP2. I swear this bug makes me lose work at least a few times a week. This was never a problem in previous versions of VFP.
>
>The worst part is that I can systematically reproduce this bug on both my desktop and my laptop, yet nobody else seems to be able to reproduce it!!!!!!!!!!!!!!!!!
>
>I'd like to pin it down to something different with my desktop and laptop and only 3 things stand out that are the same with my laptop and desktop that may be different than other people's setup:
>1. Vista Ultimate (anybody else running Ultimate?)
>2. 3GB-4GB memory(anybody running this much?)
>3. AVG Antivirus Network Edition (anybody running this AV?)
>
>Thanks so much, this bug is causing me to lose work many times a week. It's gotten so bad that I keep notepad open, and before I try to save a report, I copy my code and paste it into notepad.

It's very possible the bug is in the xbase code of the Report Designer and not the core reporting engine. The good news about that is that the xbase code is on CodePlex so *WE* the community can make bug fixes and enhancements as we see fit. If you have a reliable reproducable scenario that you can describe, and others can repeat the steps and get the same behavior, someone may be able to track down the bug and suggest a fix for CodePlex.
Cathy Pountney, Microsoft Visual FoxPro MVP
Memorial Business Systems, Inc. (www.mbs-intl.com)

My Website: (www.frontier2000.com)
My Blog: (www.cathypountney.blogspot.com)
My Book: The Visual FoxPro Report Writer - Pushing it to the Limit and Beyond
Free MSDN Article: What's New in the VFP 9.0 Report Writer
Free MSDN Article: The VFP 9.0 Report Writer In Action
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform