Access: The DB that will not die (1 Viewer)

isladogs

MVP / VIP
Local time
Today, 07:49
Joined
Jan 14, 2017
Messages
18,186

jdraw

Super Moderator
Staff member
Local time
Today, 03:49
Joined
Jan 23, 2006
Messages
15,364
I agree that the intended move to include web applications in MS Access was to expand the user base as Colin noted. Too often it seemed that Access had been forgotten when newer versions of Office products were being identified and heavily marketed. Many asked -What about Access? with very little positive info from M$oft. Many user groups and forums kept asking, and even wrote articles on the usability and growing installed base to support the longevity of the product. It seemed M$oft treated Access like the red headed stepchild. The most positive Access news from M$oft came about a year ago from Michal Bar, after ~15 years of growing uncertainty. There has been an effort within to bring Access documentation current and consistent.

The author seems focused on the DB part and not the RAD/FE to anything aspect of Access.

I have experienced how querying/extracting and reporting from Oracle databases was supported and simplified by using MS Access (ODBC). Also developing related and managed subsystems in Access was quite cost effective. My thinking is that Access is probably used within those organizations identifying Oracle, MySQL, SQL Server, PostgresSQL... more than suggested in the article.
Here's to the next 10 years!!!
 
Last edited:

gemma-the-husky

Super Moderator
Staff member
Local time
Today, 07:49
Joined
Sep 12, 2006
Messages
15,614
The thing is, the same people who dismiss robust carefully designed access databases, never see the parallel with allowing a proliferation of poorly designed mission critical excel spreadsheets within their businesses.

"do you want to open the spreadsheet read only?"


All they (ie MS) need to do with access is
a) improve the security model. Let Access have "access" to the backend database without the user needing full permissions on the folder.
b) find a way to run a multi user database over a WAN. eg Back end access database in the cloud.

Personally, I don't think access is about the "power-user" so much. That power user is likely to apply the same tools he uses for a spreadsheet, and then wonder why things are hard.

I think it's more about a competent, professional developer applying a carefully thought out design to the end database, and thereby creating a robust and friendly experience for the user.

A great deal of this is actually to restrict the user (including the designer) from using every tool that access provides. That's why you need a lot of code, defensive code, inside databases.
 
Last edited:

sonic8

AWF VIP
Local time
Today, 08:49
Joined
Oct 27, 2015
Messages
998
All they (ie MS) need to do with access is
a) improve the security model. Let Access have "access" to the backend database without the user needing full permissions on the folder.
b) find a way to run a multi user database over a WAN. eg Back end access database in the cloud.
They did that already!

The special Access backend type you need to use for that is called SQL Server!


No, seriously, Access´ strength (and gravest weakness) is that is just file based. So, it total depends on file system level access to any database file. Obviously file system permissions and the risk of corrupting files apply then.


Once you decouple an Access frontend from file system based access to the backend you need an active component on the server to manage access to the data. Such an component is a database server. So, there we are. Install SQL Server and you get what you asked for right away.
 

gemma-the-husky

Super Moderator
Staff member
Local time
Today, 07:49
Joined
Sep 12, 2006
Messages
15,614
Yes, but with SQL Server you need an additional skillset that you don't need with Jet/Ace,
 

sonic8

AWF VIP
Local time
Today, 08:49
Joined
Oct 27, 2015
Messages
998
Yes, but with SQL Server you need an additional skillset that you don't need with Jet/Ace,
If Access had the additional features you wished for, you would also need an additional skillset to handle them properly.
 

Pat Hartman

Super Moderator
Staff member
Local time
Today, 03:49
Joined
Feb 19, 2002
Messages
42,981
I don't think anyone actually wants "Access" BE's which are not even Access at all but Jet or ACE to be available over the internet. They want SOME BE and it should be one designed to do that like SQL Server. What MS needs to do is to figure out how to make the ODBC interaction between the Access FE and the RDBMS BE more efficient. Access is very chatty to which anyone who has looked at traffic between Access and the RDBMS can attest. Somehow web apps do this without a problem. Access needs to do this also.

All this business of SharePoint and web development is not Access and no existing Access app could be converted to use the web. Starting from scratch to build a web app with Access was simply a non-starter and didn't satisfy the actual need. "Access" doesn't need to run in a web browser. It can run fine as a client/server app on the local PC, it is the DATA that must be accessible remotely and Microsoft has never really gotten this concept which is why they have had four failures attempting to webify Access.

The author of the article that started this thread may write books but he certainly isn't knowledgeable about Access. Anyone who compares Access with a RDBMS doesn't know what Access actually is. Access is a RAD application tool. It creates forms and reports and code and queries. It is NOT a database engine. SQL Server is a RDBMS. It is NOT an application development tool. It manages data.

Jet and ACE are the database engines that hold the Access application objects. Access is the SSMS to Jet and ACE. For these two reasons, many people conflate the products. Windows uses Jet for certain data management functions and it does it WITHOUT ever having Access installed. Access is dependent on Jet or ACE to hold its FE objects but NOT data. Access can access data in any ODBC compliant product which includes dozens of RDBMS as well as products like Outlook and Excel so Access is not reliant on Jet or ACE as a data store.
 

isladogs

MVP / VIP
Local time
Today, 07:49
Joined
Jan 14, 2017
Messages
18,186
Thanks for the link. A good response.

The original article has certainly got a lot of attention here and elsewhere including UA and MSDN forums. Perhaps that was its main purpose.

Although the author did make some valid points, the consensus from a large number of respondents at seems to be that the points made by him are highly selective and that he is ignoring or misrepresenting anything that doesn't fit his conclusions.
 

gemma-the-husky

Super Moderator
Staff member
Local time
Today, 07:49
Joined
Sep 12, 2006
Messages
15,614
@Pat

I am sure the reason Jet/Ace back ends get conflated with Access is simply because MS ship Access as an integrated solution. Users (eventually) realise they can split a database into an Access front end and an "Access" back end, and therefore wonder about putting that Access back end into the cloud, to improve connection possibilities.

Coincidentally there is another thread current about using one drive/dropbox to store an "Access" back end.

As you mention, Windows comes with Ace/Jet support, and you can find .mdbs and probably .accdbs somewhere on your hard disk, without installing Access at all.
 

Pat Hartman

Super Moderator
Staff member
Local time
Today, 03:49
Joined
Feb 19, 2002
Messages
42,981
I am sure the reason Jet/Ace back ends get conflated with Access is simply because MS ship Access as an integrated solution
That doesn't explain why Microsoft's own SQL Server sales team doesn't know that Access isn't ACE. The MS SQL Server team itself has been responsible for several of the "Access is dead" rumors. Back in 2000 (or maybe 2002) when Access first shipped with a desktop version of SQL Server, the first rumors of Access' demise surfaced. Then again in 2007 when the Access team took Jet and turned it into ACE, the SQL Server people again spread the word - Access is dead because they thought Jet was Access.

Jet can't open .accdb's. You need to actually install ACE to be able to use an .accdb from some application other than Access.

Access did not originally ship with the Jet engine. I think 2.1 was the first Access version that installed Jet if it wasn't already installed.
 

Users who are viewing this thread

Top Bottom