Search results

  1. B

    Future of Access

    There was no explanation, no advance warning, not even a landing page, it just suddenly stopped working. Perhaps some of the UA ex-admins that are AWF members can elaborate?:unsure: Shortly before UA went offline, I offered to start a GoFundMe campaign to raise money for improvements and...
  2. B

    Future of Access

    And vba got left out because it's not compatible with web applications. Excel, Word and other Office components also have desktop, mobile, and web versions. Is MS also going to deprecate their desktop and mobile versions to maintain a single web code base?
  3. B

    Use Windows Authentication for several Access FE's to connect to SQL Server backend

    Okay, so then I don't need to specify a user ID and password in my dsnless connection string code? strConnectionString = "ODBC;DRIVER={sql server};" & _ "DATABASE=" & DatabaseName & ";" & _ "SERVER=" & ServerName & ";" & _ "Trusted_Connection=YES;" End If End If...
  4. B

    Microsoft’s “Premier” Mix-Up: A Tale of Access and Amnesia

    So much for the "Premier UA", and now they are no more.
  5. B

    Future of Access

    33 years since Access debut, and it's still alive and kicking!.. This defies MS logic. I think that Microsoft is just not making the kind of money they'd like to make from the millions of Access applications out there. Throughout the years, Microsoft has tried to persuade migration to DotNet...
  6. B

    Future of Access

    Does anyone remember Crystal Reports? Microsoft used to bundle it with Visual Studio 2003 and then they replaced Crystal with SQL Server Reporting Services (SSRS).
  7. B

    Future of Access

    Back in the 1970's and 80's I used a mainframe based report writing tool named FOCUS that had the ability to link with all kinds of datasets. It also had a native datastore, but unlike Access, it was hardly ever used for storing data. I don't see Access as stepping on SQL-Server's toes. I see...
  8. B

    Use Windows Authentication for several Access FE's to connect to SQL Server backend

    Yes, that's how I envisioned it working, but will SQL Server 2022 Enterprise Edition transparently know each different user that's connected to it via Windows Authentication, and can each user have different dba permissions, or is it one service account, or one role, for everyone in the same AD...
  9. B

    Future of Access

    Despite the lack of familiarity with Access, and IT's not liking it, I know for a fact that several State an Federal agencies have thousands of departamental Access applications running since the 1990's and they have upgraded them throughout time, e.g. converting from mdb's to accdb's...
  10. B

    Future of Access

    We are also concerned that for security purposes, Microsoft will restrict VBA from being able to manipulate the Windows Filesystem, e.g. FSO, Shell Commands, Automation, etc. Web Applications are stateless with no binding. That was main reason for Classic Outlook being replaced with webmail...
  11. B

    Use Windows Authentication for several Access FE's to connect to SQL Server backend

    Is it possible for Access frontends to dynamcally connect to a SQL Server backend using Windows Authentication without users having to enter any login credentials? e.g. A dozen Access application users, each with unique Windows login ID's, linking to the same SQL Server backend with a dsnless...
  12. B

    Future of Access

    I think MS will never retire Access because many government agencies and private enterprises have Access applications running for several decades, and the time and cost to convert them to web applications is significant.
  13. B

    Future of Access

    Hello Everyone, I had recently joined the UtterAccess forum, but unfortunately that site was permanently shutdown without any advance warning. I am a team member of four Access developers and we are concerned about the stability and future of Access.
Back
Top Bottom