Feedback by UserVoice

Ananda Sim

My feedback

  1. 83 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    26 comments  ·  Access (Desktop Application) » Datasheet  ·  Flag idea as inappropriate…  ·  Admin →

    Note that typically the reason this happens is that there is code behind the datasheet form that modifies properties on the form or controls (e.g. Textbox.Locked). Access intends to save the datasheet column widths without saving the properties changed in code, and that process was not working as expected. We are planning to fix this, but in the meantime, you may be able to work around this if you can avoid changing form/control properties in code (e.g. by using Conditional Formatting instead)

    Ananda Sim supported this idea  · 
  2. 47 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Ananda Sim commented  · 

    This proposal overlaps "Import From Excel" proposal

  3. 23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    Ananda Sim supported this idea  · 
  4. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Access (Desktop Application) » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Ananda Sim shared this idea  · 
  5. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Access (Desktop Application) » Datasheet  ·  Flag idea as inappropriate…  ·  Admin →
    Ananda Sim shared this idea  · 
  6. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    Ananda Sim supported this idea  · 
    An error occurred while saving the comment
    Ananda Sim commented  · 
    Ananda Sim shared this idea  · 
  7. 56 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    Ananda Sim supported this idea  · 
  8. 310 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    29 comments  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback.

    In terms of setting SQL Server as the default database format, that is currently not in scope for the Access product. We have provided and will continue to provide efficient methods to integrate your Access data with SQL server, and the team will continue to develop more features that streamline the data migration experience (see https://support.office.com/en-us/article/migrate-an-access-database-to-sql-server-7bac0438-498a-4f53-b17b-cc22fc42c979)

    However, the ACE database engine has and will continue to be Access’s central data storage unit.

    There are new features coming soon that will improve the Access: SQL experience, and we are excited to share this news. Please stay tuned! :)

    Ananda Sim supported this idea  · 
    An error occurred while saving the comment
    Ananda Sim commented  · 

    Yes, I support making the ACE to SQL Server bridge more comprehensive, overcoming glitches and differences between the current ACE - ODBC driver - Jet.

    I'm encountering NVARCHAR(MAX) not working properly against MEMO, so I'm using NTEXT for the time being. I've left the mapping of double to SQL Server float/real instead of the more precise data type.

    SQL identity column mechanism doesn't generate a number at the same event as Autonumber.

    The bit field has a null state that does not match Access boolean field

    Those kind of things.

    Improve ACE - ODBC driver if possible. Don't weaken Access by stripping out ACE and making the old Access Data Project

  9. 15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Ananda Sim commented  · 

    You can't switch out the Access backend for anything. Access Forms, Reports and Querys are intimately bound to ACE - the way the Form behaviour handles the Update event, Autonumber event is tightly intimate to ACE (the engine formerly known as JET). The field types in SQL Server have some compatibility with ACE field types but that's similar features, they are not the same.

    Access Forms and Reports without ACE is the old Access Data Project file format - I used that once and the integration layer was so thin, it was pale and lacking richness

  10. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    Ananda Sim shared this idea  · 
  11. 12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    Ananda Sim supported this idea  · 
  12. 12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    Ananda Sim shared this idea  · 

Feedback and Knowledge Base