Blog Post

Access Blog
1 MIN READ

Join the Access developer research panel

lindalu-MSFT's avatar
lindalu-MSFT
Icon for Microsoft rankMicrosoft
Sep 05, 2024

The Access developer research panel is comprised of Access developers who will help shape and influence the product evolution. By participating, you have the opportunity to help us prioritize upcoming features, share pain points, and provide your scenarios to help us improve. As a member of the research panel, you will receive invitations to participate in user research studies. You can decide how frequently you want to participate and which studies to complete. You can opt out of the panel or any study at any time. This is the overall Microsoft 365 developer panel, but we'll be send out specific Access surveys so you know when to opt in. 

 

As we commence FY25 planning for new Access features, your input is requested!

 

Join the Access developer research panel

 

The Access Team

Updated Sep 09, 2024
Version 3.0

27 Comments

  • The Feedback Portal replaces UserVoice. We recently (last month) fixed many of the issues with the Feedback Portal so it is much more usable and easier for us to triage. We have an issue in that "Access" is the first topic and 80% of the feedback is because they can't access their Xbox subscription, or they can't access their OneDrive, etc. They think "access" is a verb and not the official Microsoft Access database management system forum. I've requested they change the name to "Microsoft Access (database)" which should mitigate this.  There is still a backlog of spam from the early release of the Feedback Portal that I'm working with the OCV team (backend to the portal) to remove. Fortunately, these comments are buried and have no votes. So, check it out, and I'm sure you'll notice the improvement. I'd also like to point out the virtually the entire team was on vacation in August so there hasn't been much feedback response from the engineers. We'll get caught up soon.

    The best way to have direct communication with the Access developers is to join the MVP program and get on the Access MVP alias. Lastly, this survey panel was created by the previous Access PM—who was also the PM for the dev program—for all Microsoft 365 developers, not just Access developers. This is the first Access-specific survey. I decided to use it for this survey because we're starting our FY25 planning and your input DOES matter. We've had a strong response so far and we thank you for taking the time.

     

    Linda (Access PM)

  • I signed up for the Microsoft 365 Developer Panel on 12 Dec 2023. Since then I have heard absolutely nothing.

    I just tried removing myself in order to 'reapply' and it automatically reinstated me but dated 9/9/2024

     

    So I am very willing to participate but am not convinced that my willingness to be involved is actually registered

     

    Colin Riddington, Access MVP

     

     

  • SysGreg's avatar
    SysGreg
    Copper Contributor

    I'm developing Access sDB's since 1991. For 15 years I had a direct email to a guy from MS Access Team. Since then he went retired. I could solve isues with him and I have reported lot of bugs including udocumented keywords and functions in Access.

    Since MS comercializatiom, frankly said MS is NOT listening. 

    I dont' how many people wrote about need of new IDE for VBA, and we still use the same we had back with access 1.0.
    Access is outdated and 15 years behind moderm IDE. And then they removeed ADP's 10 years ago.

    DatePicker, Calendar controls, etc are made in 90's same time cinemas played Back to the Future...

    MS Access has been abandoned many years ago and there is no fresh blood to push the project forward.

    On the other hand the beauty with Access is that apps made in 90's still work well. :))

    Why there is no Access Runtime for Mac OS? It would be a huge boost being able to develop for Mac. Huge!
    Ms Access Team start to listen, please!. Not sure the new portal helps, but let's give them a chance.

    Greg

  • Curious, worked fine for me?

     

    Try a different browser maybe?

     

    Here's the expanded url from Linda's link:

    https://ux.microsoft.com/Panel/M365Devs?utm_campaign=FY25planningsurvey&utm_source=AccessCommunity&utm_medium=blog

     

    and once you're on that page, here's the URL to actually signup to participate in the panel itself:

    https://ux.microsoft.com/Panel/SignIn?Panel=M365Devs&Query=%3Futm_campaign%3DFY25planningsurvey%26utm_source%3DAccessCommunity%26utm_medium%3Dblog

     

  • marco020's avatar
    marco020
    Copper Contributor

    Hi there,

     

    I wanted to join, but the link in the first post of Linda Lu Cannon, leads to a script-error-page. 

    Thx. for fixing this.

  • Linda,

     

    Would you put this in the context of the Feedback Portal.  How does this differ?  Does this replace the former?  Are they complimentary in some manner.  I'm trying to understand what each is/does, where to actually invest time and energies into.  Which one you are actually paying attention to and in which way?

     

    I was always under the impression that UserVoice and now Feedback Portal was the means for the average user to communicate bugs, requests, frustrations, ... to you.  Has this now changed?

     

    Thank you.

  • HeinziAT's avatar
    HeinziAT
    Brass Contributor

    Let me be honest: If you want feedback from developers, provide us with a way to submit bug reports and actually get a response from the development team. You know, something like a github issue tracker.

     

    Yes, there's the feedback button in MS Access, but us mere mortals won't even get a response there. Currently, the only way to get the attention of the MS Access dev team is by bothering one of the MVPs (i.e., by creating extra work for those hard-working volunteers).

     

    We're developers. We know how to write bug reports and how to create minimal reproducible examples. Telling us to fill out surveys where we "rank the likelihood of recommending feature X to a friend on a scale of 1 to 10" instead just adds insult to injury.