Microsoft Access is a database management system from Microsoft that combines the relational Microsoft Jet Database Engine with a graphical user interface and software-development tools.
$139.99
per PC
Quickbase
Score 8.6 out of 10
N/A
Quickbase helps users tackle any project, no matter how complex. Quickbase helps customers see, connect and control complex projects. Whether it’s raising a skyscraper or coordinating vaccine rollouts, the no-code software platform allows business users to custom fit solutions to the way they work – using information from across the systems they already have.
$700
per month
Microsoft SQL Server
Score 8.7 out of 10
N/A
Microsoft SQL Server is a relational database.
$1,418
Per License
Pricing
Microsoft Access
Quickbase
Microsoft SQL Server
Editions & Modules
Microsoft Access
$139.99
per PC
Enterprise
Full Customizable
per month/billed annually
Business
Starting at $2,200
per month
Team
Started at $700
per month
Subscription
$1,418.00
Per License
Enterprise
$13,748.00
Per License
Offerings
Pricing Offerings
Microsoft Access
Quickbase
Microsoft SQL Server
Free Trial
No
Yes
No
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
Yes
No
Entry-level Setup Fee
No setup fee
Optional
No setup fee
Additional Details
—
Quickbase offers three key plans, with feature distinction, simple and consistent entitlements, and a flexible licensing model, giving users the option of either user based or usage based licensing across all 3 plans.
Visual FoxPro is a discontinued software, and no longer has support. Also, very few people still use it, or ever know how to use it. Excel is very popular, but [Microsoft] Access can do things like data joins much easier and faster
Although SQL is a full-blown platform for heavy database management, Microsoft Access serves the purpose perfectly for small and mid-scale enterprises. It is also perfect for people just getting started with database management. The graphical user interface is a major plus …
Unlike enterprise-level databases, MS Access doesn't require setting up a complex server environment with user security schemes. It's an excellent tool for small scale databases where purchasing and setting up a product like MS SQL Server could be an overkill. Unlike …
Microsoft Access is a bit dated compared to other database tools. It is slower, not able to handle quantities of data that are as large as the other tools, and a bit more finicky. However, it is sometimes the preferred tool for some clients. It also has a lower barrier to entry …
Verified User
Employee
Chose Microsoft Access
MS Access is the little brother to all these products. In no way is it as feature-rich as the competition I have selected. It is, however, great when used properly. It does not have the same level of security, availability, access, or recoverability as anything listed above. …
Access is more robust than Excel in terms of data-centricity and robustness. It however isn't meant to support an enterprise-level use case like SQL Server is. That sweet spot in the middle (a departmental solution that requires more than Excel can offer) is the sweet spot for …
We enjoyed the cloud-based set up of Quick Base. Microsoft Access also required more detailed database knowledge. Microsoft Project required expensive user licensing. We also need a program that would run it easily on Apple iPads.
Quick Base is 1000 times more intuitive and does a lot of the work for you. Microsoft Access is very much for users that actually do know how to code-if you ask me.
It's a tie. Quick Base is more stable and easy to access (ironic since Microsoft Access has the word access in the name) since it's a hosted online, but the ability to integrate (especially with Microsoft products) and customize forms and reports makes development, as it …
Before using quickbase we primarily used Microsoft Access databases for our quick turn around projects, and QuickBase's secure web based platform resolved a lot of our access on our corporate server issues.
Microsoft Access was one of the DB programs that I have used in a job previous to my current one. I found it to have many more features than Quickbase does but it was a lot harder to set up and maintain. Also, it was harder to share among multiple teams. I basically feel that …
Prior to Quickbase, we used Microsoft Access. The limitations were that it was not available on the cloud and coworkers were getting locked out of the database. You could not make development changes until everyone was out of the database.
If you don't know any programming languages, it's no problem to get started with Quick Base. On-line guides and prompts, plenty of examples and help are always available. There are template sample databases available for modification, and these provide a great opportunity to …
Microsoft Power Apps and OutSystems both were very robust, but felt overwhelming compared to Quickbase.
Verified User
Contributor
Chose Quickbase
I have personally used Quickbase and Salesforce and am so much more impressed by Quickbase. Salesforce puts so little power in your hands, for any change you have to ask their developers and it comes with a big price tag and time lag. Quickbase is easy and nimble and you can …
Mhelpdesk didn't allow us to create and customize exactly what we need, unlike Quichbase. I have nothing against Mhelpdesk [but] we just needed something a little more [suitable for our demands]. Our technical users were able to pick up what we designed much faster than Mhelpdes…
Verified User
Engineer
Chose Quickbase
I like the web functionality and the ability to access Quick Base from anywhere
QuickBase is adaptable, easy to use and can scale quickly. With either option for a simple drag and drop solution or a more complex code written for a specific application, QuickBase is clearly the winner here.
Creative Operations - Brand Marketing - Business Solutions & International
Chose Quickbase
Quick Base was MUCH more flexible and utilitarian. It did not restrict us, or make us conform our processes to their software, as many other solutions do. It has back ups, security, and support so that we are not alone. The community forums are great too. Lots of learning …
Microsoft Access while a data tool cannot scale to number of concurrent users or the great amount of files needed to run a business. Microsoft Access can attach to sql server as a backend but the interface is still limited to less than 20 concurrent users at a time.
Verified User
Technician
Chose Microsoft SQL Server
Microsoft SQL is slower than MySQL and Access but far more feature-rich and reliable. Access is almost obsolete nowadays, so not too many people are considering it, but unless budget or an open-source ethos is a factor, Microsoft SQL is superior in every way. Many commonly used …
All of the platforms have their own benefit. I was not the decision maker in selecting Microsoft SQL Server, as it was already being utilized when I joined the company, 7 years ago. I can say that I feel more comfortable with utilizing this platform as opposed to the other ones.
The free version is very powerfull and easy to install and use for small companies. Going to Professional and Standard, gives you all the support and the flexibility needed. It is known within the Database Administrator crew, and you can get support very easily over the …
I use Crystal and Microsoft SQL Server with each other. Each has a unique role that it brings to every query. Microsoft SQL Server allows me to write and refine my base query. Crystal allows me to take that query and make it more visually appealing and easier to interpret.
SQL Server is a better choice for quick time to market solutions and for easier maintenance. Oracle Database setup and programming to support solutions has a harder learning curve and it requires more time and effort to hit the ground running.
I started working with databases many years ago with Access, which allows you to create relational database and provide an old-fashioned desktop interface. I had a look at Oracle but I never had the opportunity to get to the bottom (also because of the budget that had the …
Years ago I used Oracle and Oracle Data Integrator and I hated it. It was cumbersome and archaic and I couldn't believe the product could be so popular. Given a database related task and a choice between Oracle or Microsoft SQL Server, SQL Server wins hands down in ease of use, …
I have used Microsoft Access, MySQL, and I have been a user of systems that run on Oracle database servers. All but Oracle are really intended for smaller scale projects and teams as they start to get slow or the performance will suffer once you start getting lots of data input …
As a Material Purchasing/Planning/inventory tracking application, Microsoft Access serves its purpose well. It's presentation is clean, data entry is simple and the ability to customize search fields is welcome. It does, however, come with some caveats; namely, when setting search filters and the need arises to back up a step or two, with Microsoft Access you have to reset, or "clear all", adding extra steps/time to a query.
I no longer think that Quickbase is the way of the future. They do not fix major bugs in a timely manner, and are releasing basic functionality behind a paywall. I believe that Enterprise Level Tier should be given certain things, like SLAs on Support and up-time. However, as a low-code no-code platform the majority of the accounts, "builders", and users are not going to be able to justify the cost of an Enterprise Tier Plan, and won't be able to use the features that Quickbase continues to advertise.
Microsoft SQL is ubiquitous, while MySQL runs under the hood all over the place. Microsoft SQL is the platform taught in colleges and certification courses and is the one most likely to be used by businesses because it is backed by Microsoft. Its interface is friendly (well, as pleasant as SQL can be) and has been used by so many for so long that resources are freely available if you encounter any issues.
Microsoft Access has not really changed at all for several years. It might be nice to see some upgrades and changes.
The help info is often not helpful. Need more tutorials for Microsoft Access to show how to do specific things.
Be careful naming objects such as tables, forms, etc. Names that are too long can get cut off in dialog boxes to choose a table, form, report, etc. So, I wish they would have resizable dialog boxes to allow you to see objects with long names.
I wish it could show me objects that are not in use in the database for current queries, tables, reports, forms, and macros. That way unused objects can be deleted without worrying about losing a report or query because you deleted the underlying object.
I'd like to see a link on email notices that take you directly into said notice. On an app that only has 1 or 2 email notices firing, there's no issue. However, we have some tools that are so complex that they have about 20 email notices firing at any given time based on the action users take. In this case, if we have to go in to modify a notice, we have to guess or scroll down the long list of notices to see which one we need to customize. It would be great if Quickbase had the URL of said notice somewhere at the footer of that notice so when Administrators click on it, it takes them into the exact notice they need to update.
When filling out or reviewing a lengthy form, I'd like to see the Save & close button, as well as a Save & next option at the bottom of the form rather than having to scroll back up to the top of those forms just to click on those choices.
Microsoft SQL Server Enterprise edition has a high cost but is the only edition which supports SQL Always On Availability Groups. It would be nice to include this feature in the Standard version.
Licensing of Microsoft SQL Server is a quite complex matter, it would be good to simplify licensing in the future. For example, per core vs per user CAL licensing, as well as complex licensing scenarios in the Cloud and on Edge locations.
It would be good to include native tools for converting Oracle, DB2, Postgresql and MySQL/MariaDB databases (schema and data) for import into Microsoft SQL Server.
I and the rest of my team will renew our Microsoft Access in the future because we use and maintain many different applications and databases created using Microsoft Access so we will need to maintain them in the future. Additionally, it is a standard at our place of work so it is at $0 cost to us to use. Another reason for renewing Microsoft Access is that we just don' t have the resources needed to extend into a network of users so we need to remain a single-desktop application at this time.
For our use-case of QuickBase, there really aren't any other products out there that can offer us the same out-of-the-box solutions they provide to us. We're also so integrated with it in our daily processes that to move away from it abruptly would cause mass chaos, so it's going to be renewed for at least the next several years.
We understand that the Microsoft SQL Server will continue to advance, offering the same robust and reliable platform while adding new features that enable us, as a software center, to create a superior product. That provides excellent performance while reducing the hardware requirements and the total cost of ownership of our solution.
Microsoft Access is easy to use. It is compatible with spreadsheets. It is a very good data management tool. There is scope to save a large amount of data in one place. For using this database, one does not need much training, can be shared among multiple users. This database has to sort and filtering features which seem to be very useful.
Quick Base has done everything we have asked it to do and then some. Our original goal was to have one system for CRM that encompassed both the sales process and the customer management. We have gone w-a-y beyond that with analytics, project management, system bug logging, and historical effort reporting.
SQL Server mostly 'just works' or generates error messages to help you sort out the trouble. You can usually count on the product to get the job done and keep an eye on your potential mistakes. Interaction with other Microsoft products makes operating as a Windows user pretty straight forward. Digging through the multitude of dialogs and wizards can be a pain, but the answer is usually there somewhere.
Once we did get Quick Base configured and customized it was reliably available when we needed it. We may have had one or two occasions when the product was inaccessible but those were few. The greatest challenge with its availability was its difficulty with integrating with our systems.
Some of our tables that hold over a million records are starting to perform poorly, with some summaries taking over 20 seconds to load. This may be an indication that it is best to archive old data when reaching large volumes like this.
While I have never contacted Microsoft directly for product support, for some reason there's a real prejudice against MS Access among most IT support professionals. They are usually discouraging when it comes to using MS Access. Most of this is due to their lack of understanding of MS Access and how it can improve one's productivity. If Microsoft invested more resources towards enhancing and promoting the use of MS Access then maybe things would be different.
If you utilize the community, the support is amazing. Unfortunately, I find their actual support system a bit underwhelming. They don't seem to have a great process for interacting directly with an issue and often sweep significant issues under the rug by categorizing them as "Enhancement" ideas or legacy items.
We managed to handle most of our problems by looking into Microsoft's official documentation that has everything explained and almost every function has an example that illustrates in detail how a particular functionality works. Just like PowerShell has the ability to show you an example of how some cmdlet works, that is the case also here, and in my opinion, it is a very good practice and I like it.
Quick Base already is having a separate portal of providing training to customers and it is very easy to use and updates as per the new features added in to the application
I was not directly involved with the initial account implementation, only a bystander. For the app I directly implemented for my department only, I wish I had know to create an app diagram first. I don't remember if that was suggested. I think that would be a great help tip tool when a new app is created, to have a page with a check list of what is needed or how to get started. If you are a regular app builder, then you can bypass it or have the ability to turn it off in the app settings.
Other than SQL taking quite a bit of time to actually install there are no problems with installation. Even on hardware that has good performance SQL can still take close to an hour to install a typical server with management and reporting services.
Excel is a fantastic - robust application that can do so much so easily. Its easy to train and understand. However - excel does not provide a reporting function and that is typically where we will suggest a move to [Microsoft] Access. [Microsoft] Access requires a little more knowledge of data manipulation.
Well, there's a plethora of low-code tools out on the marketplace and, you know, there's a reason that we've decided to partner with QuickBase because it has all the right balance of the ability to integrate with the ability for a citizen developer to create apps successfully. So if you look at something like Zo Ho's low-code offering, for example, yes, there are some similarities there, but they're really dependent on all of their other licensed products to get you where you want to be, where with QuickBase you have the ability to truly create something custom.
[Microsoft] SQL Server has a much better community and professional support and is overall just a more reliable system with Microsoft behind it. I've used MySQL in the past and SQL Server has just become more comfortable for me and is my go to RDBMS.
It has evolved really well with our company, but there is a hard limit to the table size that has begun to affect us and not let us grow. The table size limit is set at 500 MB and we have had to jump through quite a few hoops to be able to get by.
ROI is HUGE. Our company saved over 3.5 million in one year alone based on developments that year in Quickbase that saved time for many teams
Less user error - implementing automations and standardized workflows has led to less user error as was previously seen by maintaining spreadsheets or Smartsheets
Increased accuracy - We went from multiple users having different versions of an Excel spreadsheet to a single source of truth for our reporting.
Increased Efficiency - We can now generate reports at any time from a single source rather than multiple users spending their time collating data and generating reports.
Improved Security - Enterprise level security on a dedicated server rather than financial files on multiple laptop hard drives.