…
Hey, congrats! Good luck!
In a perfect world, yes, they have very different functions.
In this real world, a lot of people who need a database and don’t understand enough to know it start using a spreadsheet as a bad substitute. Then they get used to that particular spreadsheet. Then they ask people to help their spreadsheet do more… 
Spam reported.
My anecdote is as a new postdoc, I was put in charge of the lab’s “databases”. They had research projects with lots of categorical data. The PI wanted all of the individual project database files combined into one master database.
A postdoc in the lab was showing me the files on the server. I asked where the database files were. Right there, he said, pointing at the Excel icons.
I say “Those are spreadsheets, where are the database files?”
“Those are our databases.”
OK. I don’t have much of a computer science background, but I’m thinking I can import all those spreadsheets into an Access database somehow.
“Does our MS Office have Access?”
“Of course we have access; you’re looking at the files on the server now, [rolling his eyes at me].”
Hopefully not spam, but Cousera.org has a free, self study “Introduction to Databases” course.
Many people treat MS Excel like a database and MS Access like a spreadsheet. There is some overlap.
I suggest that Microsoft combine the two programs and call it MS Excess…
Database management jobs usually have a more detailed description of the skills required. If you don’t understand the details then you are probably not qualified for that position. It can be a confusing term as companies use it to describe whatever “they” think it means. But IMHO nothing done in Excel will qualify you for a database job.
Not really… Microsoft’s real database product is Microsoft SQL Server in one of its flavors.
Access is like a toy database by comparison.
But yeah; database manager is more of a description of someone who manages a database- the collection of data. They’re probably responsible for making sure that process and program safeguards are in place to make sure that data integrity is maintained, and that the tables are appropriately indexed and normalized to get the data in and out efficiently. They’re not usually responsible for making sure the actual server stays up, or that it has enough memory or disk space.
Database administrators are the people who actually maintain the various servers and balance the resources between the various databases on each. If they’re concerned with the actual data or queries run on the databases, it’s likely because the queries or databases are poorly designed and eating excess resources at the expense of other databases on the same server.
SalesForce isn’t a database management system. It’s a customer relationship management (CRM) system.
Also a Database Administrator (DBA) tends to be involved more in building and maintaining stuff like user access, permissions, underlying maintenance and infrastructure of large enterprise databases like Oracle, SQL Server, DB2, Apache HBase.
Anything using Excel or Access is usually just “fucking around making lists” IMHO. 800 accounts is relatively small for a database (I routinely work with SQL Server databases of hundreds of thousands or several million records). But it’s really more about how you are using them. Are you creating data relationships (ie many to one, many to many)? Are you normalizing data (ie using lookup reference tables so as to avoid duplicate or redundant entries)? The main difference between making lists in Excel and managing a database is the ability to structure the underlying data.
I see that all the time and it is hard to explain to people that, yes, you can achieve roughly the same results for smaller datasets and less complex requirements using either Excel or Access but the underlying concepts are completely different and which one you choose will almost always have serious implications down the road. Excel is a spreadsheet and Access is relational database but that is a difficult thing for most casual users to grasp.
I don’t get all the putdowns for MS Access. I am both an expert SQL Server and Oracle developer and a fairly proficient DBA in both as well. I know relational databases like the back of my hand and yet I started out using Access for ad-hoc database work and then moved up to more complex Access projects before the projects I needed to work on simply got too big and complex for it to handle well.
However, I still use Access all the time for minor projects. It is the best tool if you just want to import a subset of data from a larger database and work with it in some quick and dirty way. It is also good for developing smaller, permanent database applications that only have a handful of users or less.
The real problem with Access is that it is much more powerful than most desktop applications and that causes people to attempt to build enterprise level applications in it that should be built in SQL Server or Oracle. That costs a lot of money though and requires significantly more expertise even if the underlying ideas are the same.
I wouldn’t blame that on Access itself though. People commonly end up with poorly thought out database applications built in Access that they shouldn’t have built to begin with. Performance usually sucks as they grow and grow, they don’t have a good backup and recovery strategy and data integrity gets iffy at best because of the very limited security model.
The good news is that it is easy for someone like me to move a set of data from Excel or Access to an enterprise level database like SQL Server if the original design can’t meet the growing demands.
MS Access has been very, very good to me. I started using Access 1.0 in the early '90s when I was an aircraft mechanic to track parts and repairs. I switched career paths in 1997 when I found that I could make a living with Access. I got so good at it that I became a Microsoft VIP for Access for 4 years. Then I had the opportunity to become an Oracle DBA and here I am today.
Access is often the right tool for the job. Using SQL Server or Oracle for many tasks is like using a sledge hammer to drive in a finishing nail.