Office 2010 beta issues
in [Forms]
|
From: Alcsy8 on 28 Mar 2010 04:28 I understand that Office/Access 2010 beta will be problem free when launched later this year. Infact I am looking forward to its launch to experience its new web features. I would like to highlight some unpredictable results when running Access 2007 runtime in XPhomeSP3 PC installed with Office 2010 beta. I also hope to get some advice on how to overcome them. On other similar PC setup without the beta, no problem. 1) Pivot Chart does not work 2) Simple function used by ribbon does not run. Public Function cmdhelp() On Error GoTo Err_Handler MsgBox "Help Me!", , "Email help" Exit_Handler: Exit Function Err_Handler: MsgBox Err.Description, , "cmdhelp" Resume Exit_Handler End Function 3) Double-Click event (Works sometime") Private Sub Description_DblClick(Cancel As Integer) On Error Resume Next Dim stLinkCriteria As String stLinkCriteria = "[id]= Forms![T_test]![ID]" DoCmd.OpenForm ("frmzoom"), acNormal, , stLinkCriteria End Sub 4) Some ribbon icons are empty. 5) Security Dialog popup even when the folder is trusted. If Access 2010 does not address the above issues, I am afraid that my program will fail on my client when they upgrade their Office to 2010. Thanks -- Alcsy8
From: Maurice on 28 Mar 2010 16:46 hmmm, question. Let's say all of the issues you described here were still there in the final product, would you ship it? So my guess is that when a couple of thousand testers have been testing this product your found issues will have been resolved once the final product ships. -- Maurice Ausum "Alcsy8" wrote: > I understand that Office/Access 2010 beta will be problem free when launched > later this year. Infact I am looking forward to its launch to experience its > new web features. > > I would like to highlight some unpredictable results when running Access > 2007 runtime in XPhomeSP3 PC installed with Office 2010 beta. I also hope to > get some advice on how to overcome them. On other similar PC setup without > the beta, no problem. > > 1) Pivot Chart does not work > 2) Simple function used by ribbon does not run. > > Public Function cmdhelp() > On Error GoTo Err_Handler > > MsgBox "Help Me!", , "Email help" > Exit_Handler: > Exit Function > > Err_Handler: > MsgBox Err.Description, , "cmdhelp" > Resume Exit_Handler > End Function > > 3) Double-Click event (Works sometime") > > Private Sub Description_DblClick(Cancel As Integer) > On Error Resume Next > Dim stLinkCriteria As String > stLinkCriteria = "[id]= Forms![T_test]![ID]" > DoCmd.OpenForm ("frmzoom"), acNormal, , stLinkCriteria > > End Sub > > 4) Some ribbon icons are empty. > 5) Security Dialog popup even when the folder is trusted. > > If Access 2010 does not address the above issues, I am afraid that my > program will fail on my client when they upgrade their Office to 2010. > > Thanks > -- > Alcsy8
From: Alcsy8 on 28 Mar 2010 23:33 Thanks that is reassuring. -- Alcsy8 "Maurice" wrote: > hmmm, question. Let's say all of the issues you described here were still > there in the final product, would you ship it? So my guess is that when a > couple of thousand testers have been testing this product your found issues > will have been resolved once the final product ships. > -- > Maurice Ausum > > > "Alcsy8" wrote: > > > I understand that Office/Access 2010 beta will be problem free when launched > > later this year. Infact I am looking forward to its launch to experience its > > new web features. > > > > I would like to highlight some unpredictable results when running Access > > 2007 runtime in XPhomeSP3 PC installed with Office 2010 beta. I also hope to > > get some advice on how to overcome them. On other similar PC setup without > > the beta, no problem. > > > > 1) Pivot Chart does not work > > 2) Simple function used by ribbon does not run. > > > > Public Function cmdhelp() > > On Error GoTo Err_Handler > > > > MsgBox "Help Me!", , "Email help" > > Exit_Handler: > > Exit Function > > > > Err_Handler: > > MsgBox Err.Description, , "cmdhelp" > > Resume Exit_Handler > > End Function > > > > 3) Double-Click event (Works sometime") > > > > Private Sub Description_DblClick(Cancel As Integer) > > On Error Resume Next > > Dim stLinkCriteria As String > > stLinkCriteria = "[id]= Forms![T_test]![ID]" > > DoCmd.OpenForm ("frmzoom"), acNormal, , stLinkCriteria > > > > End Sub > > > > 4) Some ribbon icons are empty. > > 5) Security Dialog popup even when the folder is trusted. > > > > If Access 2010 does not address the above issues, I am afraid that my > > program will fail on my client when they upgrade their Office to 2010. > > > > Thanks > > -- > > Alcsy8
From: Dennis on 29 Mar 2010 01:01 Maurice, You have a good point. But I wonder, were there a couple of thousand tester for Windows ME and Vista? Did they fix all of the bugs before they released it? No. And which operating system crashed while Bill Gates was showing off the release version (I think) to a large audience? Granted ME was much worse the Vista with the bugs, but still. Hopefuly Microsoft has learned from it past. I realize that this is a Microsoft forum, but we also need to be honest. Dennis
From: Mike Painter on 29 Mar 2010 01:23 Dennis wrote: > Maurice, > > You have a good point. But I wonder, were there a couple of thousand > tester for Windows ME and Vista? Did they fix all of the bugs before > they released it? No. > > And which operating system crashed while Bill Gates was showing off > the release version (I think) to a large audience? > > Granted ME was much worse the Vista with the bugs, but still. > > Hopefuly Microsoft has learned from it past. I realize that this is a > Microsoft forum, but we also need to be honest. > > > Dennis In the old days beta testing was done by people who usually signed non disclosure agreements. Today's method has a lot of advantages as at least a large set of people do know what the term means and is willing to live with it. *Nobody* is ever going to release a trouble free beta of anything, there would be no point to it. The final goldern release will also have bugs but hpoefully a lot fewer of them. IBM's major study many years ago indicates that in any major software package fixing a bug has about a 50% chance of revealing or causing another one. I've seen this once in a while in long used "stable" programs I've written. In a couple of those cases finding theproblem was very hard as Access essentially let me get away with something that it should have "caught" The last one had me moving a subform onto a tab control. The unbound textbox that linked it to another subform stopped working. It's name was the same as that of another field but it worked for years.
|
Next
|
Last
Pages: 1 2 Prev: code closing multiple reports Next: automate copying text in Word doc to Access db |