Thanks Rick! Seems too easy ...
If a bug is really a bug, MS will correct it for free?! Or simply they give you a workaround? Anyway I have a little good news! I have just discovered to have two free support ticket for my copy of VFP9! ... and I'm going to use the first! Probably anyone of you having payed for VFP has these two free support ticket. Gianni On Fri, 13 Mar 2009 02:27:09 -0400, "Rick Schummer" <[email protected]> wrote: >Milind Lele from Microsoft explains it like this: > >-------------------------------------- >Yes, this is correct. VFP bug reports need to go thru product support. > >Connect is great when there is continuous development and reported issues >and suggestions can get rolled into the next release. > >Since VFP is in support mode only, the best way to get an issue reported and >fixed is through product support. >-------------------------------------- > > >So I followed the links in your post and found that if I want to post a bug >it will cost me money to go through Product Support Services (PSS). So I >asked Milind about getting charged to report problems with Microsoft's >product and he responded to me with this: > > >-------------------------------------- >Actually for a valid bug, the charges get reverted. The quickest way to get >a fix is to have a hotfix issued. And the fastest and surest way to do that >is to create that request from support. >-------------------------------------- > >So there is no charge for valid bugs. I guess you really should ensure the >issue you are figuring out is a bug and not something you created in your >own code. I know I have made mistakes in my code that lead me to consider >the possibility of a bug in VFP. You might want to flush it out here on >ProFox with your peers to ensure it really is a problem and not your >imagination or own buggy code. Then call Microsoft. > >While Connect was efficient and free no matter what, I feel that talking to >a real person at PSS is well worth the cost if I make a mistake. At least I >know someone is looking into it, and knowing the guys at PSS who support >VFP, it is a good deal. They are top notch. VFP really felt like a >red-headed-step-child on Connect. You never felt like the issue was being >processed through the normal channels. The bugs got logged under Visual >Studio and passed along to the VFP team. Yes, they got it, but all the bug >reports were closed by the VS team when they got passed along. Feedback did >not follow the normal channels back to the developer either. While it sounds >unfortunate at first, I think this might be the best route overall. > >Rick >White Light Computing, Inc. > >www.whitelightcomputing.com >www.swfox.net >www.rickschummer.com > > > > >-----Original Message----- >From: [email protected] [mailto:[email protected]] On >Behalf Of Gianni Turri >Sent: Wednesday, March 11, 2009 06:07 AM >To: [email protected] >Subject: Visual FoxPro is no longer supported through Connect ?! > >Hi all! > >Two days ago I submitted a VFP bug through Connect and today I received this >email. > >>Visual FoxPro is no longer supported though Connect. > >What is the correct place to post a bug in the hope they correct it? > >TIA, >Gianni _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
