Access frontend size growing over 1.9Gb while connected to Sharepoint 365












0















I have a ms-access frontend for stock count connected to sharepoint 365. Problem is it has swelled to 1.9GB and with every passing stock count, it is increasing size.
If I do not cache sharepoint list, reports will take forever to generate.



I am concerned whether ms-access 2GB limit will affect my program and what will happen if the size limit gets breached?










share|improve this question


















  • 1





    If you can't run a compact & repair to hold the size down, or split data somehow between one or more attached database (files), it will cease to operate when reaching 2 GB. It's a hard limit.

    – Gustav
    Nov 23 '18 at 14:40











  • Thank you Gustav. Actually it is not happening if Access database are split and then reconnected but it is happening for sharepoint lists. Does this happen for SQL tables as well when connected as backend?

    – Sohaib Ahmed Siddiqui
    Nov 23 '18 at 17:05













  • Sorry, can't tell. I've never used SP lists for a little testing, nothing serious.

    – Gustav
    Nov 23 '18 at 18:46











  • No issue or problem or size increase with SQL back end tables. All data is held on the server - so no local file limit size, or growth of the front end part will occur.

    – Albert D. Kallal
    Nov 23 '18 at 22:53











  • @SohaibAhmedSiddiqui Is the sharepoint cache a single table? If it is multiple tables, can you cache it in multiple local linked database files? Even if its currently in one table, perhaps it could be separated into multiple tables? ... and still maintain performance gain by doing so?

    – C Perkins
    Nov 24 '18 at 3:55
















0















I have a ms-access frontend for stock count connected to sharepoint 365. Problem is it has swelled to 1.9GB and with every passing stock count, it is increasing size.
If I do not cache sharepoint list, reports will take forever to generate.



I am concerned whether ms-access 2GB limit will affect my program and what will happen if the size limit gets breached?










share|improve this question


















  • 1





    If you can't run a compact & repair to hold the size down, or split data somehow between one or more attached database (files), it will cease to operate when reaching 2 GB. It's a hard limit.

    – Gustav
    Nov 23 '18 at 14:40











  • Thank you Gustav. Actually it is not happening if Access database are split and then reconnected but it is happening for sharepoint lists. Does this happen for SQL tables as well when connected as backend?

    – Sohaib Ahmed Siddiqui
    Nov 23 '18 at 17:05













  • Sorry, can't tell. I've never used SP lists for a little testing, nothing serious.

    – Gustav
    Nov 23 '18 at 18:46











  • No issue or problem or size increase with SQL back end tables. All data is held on the server - so no local file limit size, or growth of the front end part will occur.

    – Albert D. Kallal
    Nov 23 '18 at 22:53











  • @SohaibAhmedSiddiqui Is the sharepoint cache a single table? If it is multiple tables, can you cache it in multiple local linked database files? Even if its currently in one table, perhaps it could be separated into multiple tables? ... and still maintain performance gain by doing so?

    – C Perkins
    Nov 24 '18 at 3:55














0












0








0








I have a ms-access frontend for stock count connected to sharepoint 365. Problem is it has swelled to 1.9GB and with every passing stock count, it is increasing size.
If I do not cache sharepoint list, reports will take forever to generate.



I am concerned whether ms-access 2GB limit will affect my program and what will happen if the size limit gets breached?










share|improve this question














I have a ms-access frontend for stock count connected to sharepoint 365. Problem is it has swelled to 1.9GB and with every passing stock count, it is increasing size.
If I do not cache sharepoint list, reports will take forever to generate.



I am concerned whether ms-access 2GB limit will affect my program and what will happen if the size limit gets breached?







ms-access sharepoint






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 23 '18 at 14:18









Sohaib Ahmed SiddiquiSohaib Ahmed Siddiqui

1




1








  • 1





    If you can't run a compact & repair to hold the size down, or split data somehow between one or more attached database (files), it will cease to operate when reaching 2 GB. It's a hard limit.

    – Gustav
    Nov 23 '18 at 14:40











  • Thank you Gustav. Actually it is not happening if Access database are split and then reconnected but it is happening for sharepoint lists. Does this happen for SQL tables as well when connected as backend?

    – Sohaib Ahmed Siddiqui
    Nov 23 '18 at 17:05













  • Sorry, can't tell. I've never used SP lists for a little testing, nothing serious.

    – Gustav
    Nov 23 '18 at 18:46











  • No issue or problem or size increase with SQL back end tables. All data is held on the server - so no local file limit size, or growth of the front end part will occur.

    – Albert D. Kallal
    Nov 23 '18 at 22:53











  • @SohaibAhmedSiddiqui Is the sharepoint cache a single table? If it is multiple tables, can you cache it in multiple local linked database files? Even if its currently in one table, perhaps it could be separated into multiple tables? ... and still maintain performance gain by doing so?

    – C Perkins
    Nov 24 '18 at 3:55














  • 1





    If you can't run a compact & repair to hold the size down, or split data somehow between one or more attached database (files), it will cease to operate when reaching 2 GB. It's a hard limit.

    – Gustav
    Nov 23 '18 at 14:40











  • Thank you Gustav. Actually it is not happening if Access database are split and then reconnected but it is happening for sharepoint lists. Does this happen for SQL tables as well when connected as backend?

    – Sohaib Ahmed Siddiqui
    Nov 23 '18 at 17:05













  • Sorry, can't tell. I've never used SP lists for a little testing, nothing serious.

    – Gustav
    Nov 23 '18 at 18:46











  • No issue or problem or size increase with SQL back end tables. All data is held on the server - so no local file limit size, or growth of the front end part will occur.

    – Albert D. Kallal
    Nov 23 '18 at 22:53











  • @SohaibAhmedSiddiqui Is the sharepoint cache a single table? If it is multiple tables, can you cache it in multiple local linked database files? Even if its currently in one table, perhaps it could be separated into multiple tables? ... and still maintain performance gain by doing so?

    – C Perkins
    Nov 24 '18 at 3:55








1




1





If you can't run a compact & repair to hold the size down, or split data somehow between one or more attached database (files), it will cease to operate when reaching 2 GB. It's a hard limit.

– Gustav
Nov 23 '18 at 14:40





If you can't run a compact & repair to hold the size down, or split data somehow between one or more attached database (files), it will cease to operate when reaching 2 GB. It's a hard limit.

– Gustav
Nov 23 '18 at 14:40













Thank you Gustav. Actually it is not happening if Access database are split and then reconnected but it is happening for sharepoint lists. Does this happen for SQL tables as well when connected as backend?

– Sohaib Ahmed Siddiqui
Nov 23 '18 at 17:05







Thank you Gustav. Actually it is not happening if Access database are split and then reconnected but it is happening for sharepoint lists. Does this happen for SQL tables as well when connected as backend?

– Sohaib Ahmed Siddiqui
Nov 23 '18 at 17:05















Sorry, can't tell. I've never used SP lists for a little testing, nothing serious.

– Gustav
Nov 23 '18 at 18:46





Sorry, can't tell. I've never used SP lists for a little testing, nothing serious.

– Gustav
Nov 23 '18 at 18:46













No issue or problem or size increase with SQL back end tables. All data is held on the server - so no local file limit size, or growth of the front end part will occur.

– Albert D. Kallal
Nov 23 '18 at 22:53





No issue or problem or size increase with SQL back end tables. All data is held on the server - so no local file limit size, or growth of the front end part will occur.

– Albert D. Kallal
Nov 23 '18 at 22:53













@SohaibAhmedSiddiqui Is the sharepoint cache a single table? If it is multiple tables, can you cache it in multiple local linked database files? Even if its currently in one table, perhaps it could be separated into multiple tables? ... and still maintain performance gain by doing so?

– C Perkins
Nov 24 '18 at 3:55





@SohaibAhmedSiddiqui Is the sharepoint cache a single table? If it is multiple tables, can you cache it in multiple local linked database files? Even if its currently in one table, perhaps it could be separated into multiple tables? ... and still maintain performance gain by doing so?

– C Perkins
Nov 24 '18 at 3:55












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53448363%2faccess-frontend-size-growing-over-1-9gb-while-connected-to-sharepoint-365%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53448363%2faccess-frontend-size-growing-over-1-9gb-while-connected-to-sharepoint-365%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Costa Masnaga

Fotorealismo

Sidney Franklin