Future of Access (7 Viewers)

Also, and most importantly, the SQL Server team thinks of Access as a competitor because they don't even know what Access is and they think of it only in terms of Jet/ACE. So they don't even understand that many production Access applications rely on SQL Server or other RDBMS as their data store.
Do you really think they are so short-sighted and superficial?

Is that more your personal perception of the situation, or where do these statements originate from?
 
s that more your personal perception of the situation, or where do these statements originate from?
Your question is a bit snarky but it's actually from personal exchanges with the SQL Server regional manager and other reps at different client installations. They are all convinced that "Access" is only an inferior database engine. They KNOW this because they were responsible for Jet and that is one of the reasons that the Access team copied Jet and turned it into ACE for A2007. The Access team wanted to make changes to Jet to make it more compatible with SharePoint and the Jet team wasn't willing. Their advice to the clients is always to keep clear of "Access" because it is limited in size and lacking in security among other issues - all of which actually are "flaws" of Jet and have nothing to do with Access the RAD tool.
 
Last edited:
MS may want Access users to migrate to PA, but if PA cannot fulfill all the needs their Access apps currently delivers. Therefore, users will continue using Access, as several have been doing for decades. MS is concerned about vba being a high security risk. That's why they wanted to retire desktop Outlook.
Fixed it for you.
 
Fixed it for you.
I said "if PA cannot fulfill..." because PA is young, Work In Progress, and may some day be as robust as Access, unless you know something we don't?

I remember you recently mimicking Access NW2 functionality with PA by making SQL Server Stored Procedures do the heavy lifting.
 
Last edited:

Users who are viewing this thread

Back
Top Bottom