Are there alternatives to Microsoft Access?
In my office, we often use MS Access for many applications (eg creating reports, data analysis and data processing) because it is convenient to use (easy data import, fast query building, easy automatization with VBA)
Unfortunately, it starts to be insufficient for me due to the size limitations of the database file. This is one thing. Another thing is that Access is often unable to execute my complex SQL queries (I omit that the SQL used by Access is limited).
Is anyone out there aware of any tools similar to MS Access that can be used with databases over 2GB?
Possibly, I am considering using Access as a front-end, but what about the back-end? Can you recommend something?
ms-access database-recommendation ms-access-2010
New contributor
add a comment |
In my office, we often use MS Access for many applications (eg creating reports, data analysis and data processing) because it is convenient to use (easy data import, fast query building, easy automatization with VBA)
Unfortunately, it starts to be insufficient for me due to the size limitations of the database file. This is one thing. Another thing is that Access is often unable to execute my complex SQL queries (I omit that the SQL used by Access is limited).
Is anyone out there aware of any tools similar to MS Access that can be used with databases over 2GB?
Possibly, I am considering using Access as a front-end, but what about the back-end? Can you recommend something?
ms-access database-recommendation ms-access-2010
New contributor
1
Your question is off-topic, but if you like the Access front end, PostgreSQL has ODBC drivers, which you can use to connect Access to a PostgreSQL backend. PG is fully open source and production worthy; there are no limitations on data size (besides your disk space).
– jpmc26
4 hours ago
1
I second @jpmc26's recommendation for Postgres. Besides being fully open source, they have an excellent community. For example, here is the novice mailing list, with the description "No question is too simple for this list."
– Wildcard
3 hours ago
add a comment |
In my office, we often use MS Access for many applications (eg creating reports, data analysis and data processing) because it is convenient to use (easy data import, fast query building, easy automatization with VBA)
Unfortunately, it starts to be insufficient for me due to the size limitations of the database file. This is one thing. Another thing is that Access is often unable to execute my complex SQL queries (I omit that the SQL used by Access is limited).
Is anyone out there aware of any tools similar to MS Access that can be used with databases over 2GB?
Possibly, I am considering using Access as a front-end, but what about the back-end? Can you recommend something?
ms-access database-recommendation ms-access-2010
New contributor
In my office, we often use MS Access for many applications (eg creating reports, data analysis and data processing) because it is convenient to use (easy data import, fast query building, easy automatization with VBA)
Unfortunately, it starts to be insufficient for me due to the size limitations of the database file. This is one thing. Another thing is that Access is often unable to execute my complex SQL queries (I omit that the SQL used by Access is limited).
Is anyone out there aware of any tools similar to MS Access that can be used with databases over 2GB?
Possibly, I am considering using Access as a front-end, but what about the back-end? Can you recommend something?
ms-access database-recommendation ms-access-2010
ms-access database-recommendation ms-access-2010
New contributor
New contributor
edited 4 hours ago
Paul White♦
50.9k14278448
50.9k14278448
New contributor
asked 9 hours ago
RicoRico
92
92
New contributor
New contributor
1
Your question is off-topic, but if you like the Access front end, PostgreSQL has ODBC drivers, which you can use to connect Access to a PostgreSQL backend. PG is fully open source and production worthy; there are no limitations on data size (besides your disk space).
– jpmc26
4 hours ago
1
I second @jpmc26's recommendation for Postgres. Besides being fully open source, they have an excellent community. For example, here is the novice mailing list, with the description "No question is too simple for this list."
– Wildcard
3 hours ago
add a comment |
1
Your question is off-topic, but if you like the Access front end, PostgreSQL has ODBC drivers, which you can use to connect Access to a PostgreSQL backend. PG is fully open source and production worthy; there are no limitations on data size (besides your disk space).
– jpmc26
4 hours ago
1
I second @jpmc26's recommendation for Postgres. Besides being fully open source, they have an excellent community. For example, here is the novice mailing list, with the description "No question is too simple for this list."
– Wildcard
3 hours ago
1
1
Your question is off-topic, but if you like the Access front end, PostgreSQL has ODBC drivers, which you can use to connect Access to a PostgreSQL backend. PG is fully open source and production worthy; there are no limitations on data size (besides your disk space).
– jpmc26
4 hours ago
Your question is off-topic, but if you like the Access front end, PostgreSQL has ODBC drivers, which you can use to connect Access to a PostgreSQL backend. PG is fully open source and production worthy; there are no limitations on data size (besides your disk space).
– jpmc26
4 hours ago
1
1
I second @jpmc26's recommendation for Postgres. Besides being fully open source, they have an excellent community. For example, here is the novice mailing list, with the description "No question is too simple for this list."
– Wildcard
3 hours ago
I second @jpmc26's recommendation for Postgres. Besides being fully open source, they have an excellent community. For example, here is the novice mailing list, with the description "No question is too simple for this list."
– Wildcard
3 hours ago
add a comment |
2 Answers
2
active
oldest
votes
Check out Linked Tables to SQL Server if you're running up against complexity requirements for your data. Basically, as you are expecting, Access would still work as your front-end and SQL Server would work as the back-end. For complex SQL statements, you can make use of Stored Procedures that you call from Access as well. If nothing else, this could give you some more time to rewrite the Access application in something a little more robust like .NET (language/platform of your choosing). Honestly though, if there's no pressing need to change out the Access application, keep it around if it's doing the job. I support clients that run tons of business functionality off of an Access front end tied to a basic availability group on SQL Server Standard Edition for high availability. It does the job just fine and it doesn't cost an arm and a leg.
add a comment |
SQL Server Express has a 10GB limit.
It should work well with MS Access as a front end.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Rico is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f229276%2fare-there-alternatives-to-microsoft-access%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Check out Linked Tables to SQL Server if you're running up against complexity requirements for your data. Basically, as you are expecting, Access would still work as your front-end and SQL Server would work as the back-end. For complex SQL statements, you can make use of Stored Procedures that you call from Access as well. If nothing else, this could give you some more time to rewrite the Access application in something a little more robust like .NET (language/platform of your choosing). Honestly though, if there's no pressing need to change out the Access application, keep it around if it's doing the job. I support clients that run tons of business functionality off of an Access front end tied to a basic availability group on SQL Server Standard Edition for high availability. It does the job just fine and it doesn't cost an arm and a leg.
add a comment |
Check out Linked Tables to SQL Server if you're running up against complexity requirements for your data. Basically, as you are expecting, Access would still work as your front-end and SQL Server would work as the back-end. For complex SQL statements, you can make use of Stored Procedures that you call from Access as well. If nothing else, this could give you some more time to rewrite the Access application in something a little more robust like .NET (language/platform of your choosing). Honestly though, if there's no pressing need to change out the Access application, keep it around if it's doing the job. I support clients that run tons of business functionality off of an Access front end tied to a basic availability group on SQL Server Standard Edition for high availability. It does the job just fine and it doesn't cost an arm and a leg.
add a comment |
Check out Linked Tables to SQL Server if you're running up against complexity requirements for your data. Basically, as you are expecting, Access would still work as your front-end and SQL Server would work as the back-end. For complex SQL statements, you can make use of Stored Procedures that you call from Access as well. If nothing else, this could give you some more time to rewrite the Access application in something a little more robust like .NET (language/platform of your choosing). Honestly though, if there's no pressing need to change out the Access application, keep it around if it's doing the job. I support clients that run tons of business functionality off of an Access front end tied to a basic availability group on SQL Server Standard Edition for high availability. It does the job just fine and it doesn't cost an arm and a leg.
Check out Linked Tables to SQL Server if you're running up against complexity requirements for your data. Basically, as you are expecting, Access would still work as your front-end and SQL Server would work as the back-end. For complex SQL statements, you can make use of Stored Procedures that you call from Access as well. If nothing else, this could give you some more time to rewrite the Access application in something a little more robust like .NET (language/platform of your choosing). Honestly though, if there's no pressing need to change out the Access application, keep it around if it's doing the job. I support clients that run tons of business functionality off of an Access front end tied to a basic availability group on SQL Server Standard Edition for high availability. It does the job just fine and it doesn't cost an arm and a leg.
answered 8 hours ago
John EisbrenerJohn Eisbrener
5,22611341
5,22611341
add a comment |
add a comment |
SQL Server Express has a 10GB limit.
It should work well with MS Access as a front end.
add a comment |
SQL Server Express has a 10GB limit.
It should work well with MS Access as a front end.
add a comment |
SQL Server Express has a 10GB limit.
It should work well with MS Access as a front end.
SQL Server Express has a 10GB limit.
It should work well with MS Access as a front end.
edited 4 hours ago
Paul White♦
50.9k14278448
50.9k14278448
answered 8 hours ago
Michael KutzMichael Kutz
2,0171111
2,0171111
add a comment |
add a comment |
Rico is a new contributor. Be nice, and check out our Code of Conduct.
Rico is a new contributor. Be nice, and check out our Code of Conduct.
Rico is a new contributor. Be nice, and check out our Code of Conduct.
Rico is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f229276%2fare-there-alternatives-to-microsoft-access%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Your question is off-topic, but if you like the Access front end, PostgreSQL has ODBC drivers, which you can use to connect Access to a PostgreSQL backend. PG is fully open source and production worthy; there are no limitations on data size (besides your disk space).
– jpmc26
4 hours ago
1
I second @jpmc26's recommendation for Postgres. Besides being fully open source, they have an excellent community. For example, here is the novice mailing list, with the description "No question is too simple for this list."
– Wildcard
3 hours ago