Changing RecordSource Causes A Reload of Sub Form Destroying References
in [Forms]
|
From: Stewart Berman on 20 Nov 2009 18:06 >Support Professional can assist you in a more efficient manner. Please be >advised that contacting phone support will be a charged call. I think I'll pass on that. If I were to pay for every software bug I hit -- in third party as well as MS -- I'd need a lot bigger revenue stream just to break even. Anyway, we developed a workaround for the symptom -- that is the bug still affects the flow but we are able to complete the process. changliw(a)online.microsoft.com ("Charles Wang [MSFT]") wrote: >Hi Stewart, >According to the current information, it is hard to give a reason why this >issue happened at some of your computers but worked on other computers with >the same Access 2007 runtime components. What I suggested before was trying >to help isolate if this is a possible problem. But since this issue is >environment specific and hard to be reproduced at our side, if you want to >track the root cause of the issue, a dump analysis is required. You need to >contact Customer Support Services (CSS) via telephone so that a dedicated >Support Professional can assist you in a more efficient manner. Please be >advised that contacting phone support will be a charged call. > >To obtain the phone numbers for specific technology request please take a >look at the web site listed below. >http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS > >If you are outside the US please see http://support.microsoft.com for >regional support phone numbers. > >Best regards, >Charles Wang
From: "Charles Wang [MSFT]" on 22 Nov 2009 21:42 Hi Stewart, For contacting CSS, if this issue is proved to be a product issue, you will not be charged at last. Anyway I am glad to hear that you have found a workaround by yourself. Best regards, Charles Wang
From: Stewart Berman on 23 Nov 2009 00:20
The problem with CSS is that you are charged first and then, IF CSS completes problem determination AND decides it is a bug you get a refund. Meanwhile they have your money for as long as it takes for them to get to the problem and forever if they can't do problem determination. I wonder how much is earned on the float. Yes, I have a workaround but the bug will probably bite a number of people and might take a few out. Hopefully, someone will hit it in the 2010 beta. changliw(a)online.microsoft.com ("Charles Wang [MSFT]") wrote: >Hi Stewart, >For contacting CSS, if this issue is proved to be a product issue, you will >not be charged at last. Anyway I am glad to hear that you have found a >workaround by yourself. > >Best regards, >Charles Wang |