Is any one using MS Access?
-
Power users can make good use of Access if they limit themselves to what they know, and they don't try to make it a multi-user application.
Agreed, that is how I use it, only when it makes sense for a specific purpose.
-
Just updated office 365 and along with it Access 2016. I've never used it. Does anyone use it? What for? and should I?
We will pry MS Access from my boss's cold dead hands. Our major backend processing uses it and we have to adapt our SQL Server processes and tables to it's limitations. Attempts to get him to recode to SQL Server have fallen on deaf ears. I've always wondered why Microsoft has not put an Access frontend to SQL Server. Drag and Drop query creation is far less intimidating than SQL and you still have the option to edit the Drag and Drop SQL generated. The Report generator would be nice for SQL Server as well.
Psychosis at 10 Film at 11 Those who do not remember the past, are doomed to repeat it. Those who do not remember the past, cannot build upon it.
-
Just updated office 365 and along with it Access 2016. I've never used it. Does anyone use it? What for? and should I?
I have been using ACCESS for 20+ years. I have a client whose entire business runs on Access based software and she has had no problems for 18 years except when MS decided to not have backwards compatibility with certain functions or features as it released new versions. I have used it to keep my consulting business client work status and billing records for most of the 20 years. A colleague and I have been using it in as part of a commercial science researcher utilized product (VB for code and Access for the database) for 10 years without any Access problems; VB has given us may more problems as MS changed, dropped, etc. functions, function calls, etc. I noted at least one commenter stated that is is a terrible product and that a great many terrible applications have been written by bad programmers using it. Well, I have done software quality assurance for JPL/NASA and I can tell you that I've seen terrible programs written in over 20 programming languages and some utilizing a number of databases for back ends. I've seen terrible Oracle and DB2 code. A terrible software architect will design terrible software; and it goes all the way down to the terrible coder creating terrible code. This is not the criteria to use when deciding if some language or database system is the correct one to use for some purpose. ACCESS is great for simple database applications. It can be used for some rather complex ones also. It depends on the design of the database, the design of the code, the amount of time you are willing to spend learning relational database design and learning to code in Access's programming language. ACCESS is worth taking a look at and getting a decent book is the first step. I've not bought a new ACCESS book since Office 2007, so can't recommend one to you.
Charles Wolfe C. Wolfe Software Engineering
-
Just updated office 365 and along with it Access 2016. I've never used it. Does anyone use it? What for? and should I?
I work as a file clerk for a government agency, and I worked with a guy who developed an Access application that parsed reports from our department mainframe into various smaller/localized reports, research tools, and worksheets for use by other clerks in our office. Some of these reports even make it all the way to department managers and HQ. It's a really handy little thing but he's not a strong programmer and the guy who actually designed it isn't around anymore. I made the mistake of mentioning I had programming skills... and here I am getting caught up in it. So when you're not able to install real technology, Access can fill the void. But it's painful. If you can convince your IT to let you use real programming tools and database libraries you'd be much better off.
-
Just updated office 365 and along with it Access 2016. I've never used it. Does anyone use it? What for? and should I?
Was my first database, it's been 3+ :sigh: years since I last used it.
-
I use MS-Access. There is no other choice if you need a multi-user database shared over a network, and you can not install SQL Server or any other database server. You cannot achieve this with SQLite or SqlServer Compact Edition.
-
I believe even Microsoft has said to NOT use Access for multi-user database shared over a network.
-
Unfortunately, it was a LONG time ago when I read that. I think it was around the time Sql Server Express came out. Google or Bing will reveal many non-Microsoft people who have had trouble with corrupted Access database files when trying to share on a network. In fact, that was what caused me to first try Sql Server Express. I was brought in to help fix an Access application that was getting corrupt access network files. So I switched the whole Access application to using Sql Server Express instead and they never had another problem. At that time Sql Server Express was limited to 5 simultaneous usage, but I think they have taken that and other limits off in the more recent versions.
-
Ah, Bing was my friend and found this: https://view.officeapps.live.com/op/view.aspx?src=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2F5%2Fd%2F0%2F5d026b60-e4be-42fc-a250-2d75c49172bc%2Fwhen_to_Migrate_from_Access.doc[^] Check round about page 8.
-
There is a Hell sepcifically for the people who thought of it. Not a circle - an entire Hell. Just for them.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver "When you have eliminated the JavaScript, whatever remains must be an empty page." -- Mike Hankey
Access front end SQL Server back end served me well for years in a large corporate environment. The report creation is a wiz , a lot easier to knock out a report that Reporting Services. I agree a large user base over a network is a bit iffy which is why I ported from an Access db back end , that said we managed up to 50 users across a network with no issues. I eventually ported it to SQL and ultimately it was "taken over" by a dot NET app , mostly because the IT dept couldn't cope with an Access App that worked !!
Mike