recyclela.blogg.se

Phpmaker migration vs development
Phpmaker migration vs development







Is this positively or negatively impacting your desire to continue to use Access?Īt the end of the day, are you getting the support you expect from your software vendor? So not only has the quantity of issues increased in recent years IMHO, but what is your impression of Microsoft’s response in resolving such issues?Īre they meeting your expectations and resolving them adequately and in a timely manner?

  • Open last used database when Access starts Not Working.
  • Action Queries Do Not Work and Crash Access.
  • Access 2016 Form Scrolling Doesn’t Work.
  • 1710 Breaks Compatibility with ACCDEs and Access Runtime.
  • Large Number incompatibility with runtime.
  • Automatic configuration of the current version of Microsoft Access has failed.
  • Record Source and Row Source Changes Not Saving.
  • Can’t create compiled version with empty procedures.
  • Microsoft Access can’t open the mail session.
  • Inconsistent state/Unrecognized format bug.
  • A few examples just of recent Access bugs, quickly pulled from this site (note I stopped logging bugs as it was becoming too time consuming, so this list is far from complete), include:

    phpmaker migration vs development

    It is clear, that the shift to continued development and releases by Microsoft has drastically increased the number and severity of bugs that we are all having to deal with and this is true for both Windows and Office. I put the question to you, with what you’ve experienced in the past 3-5 years (since Office365), do you feel that Access will survive? Or has Microsoft put the nail in its coffin?









    Phpmaker migration vs development