none
Access 2013 vs. 2016 RRS feed

  • Question

  • Somewhat of a beginner here.

    I created a database for my company and used Access 2013.  At the time that's what I had on my personal computer to build it.  We recently got Access 2016 at the office for a few of us to use this database.  Since releasing it I have tried to use 2016 to add some additional features such as forms and buttons to launch those forms, however, when testing the new buttons the database freezes.  The tables that the forms are referencing were also created in the 2013 version.

    I set it up as a back end database/tables and separate file for the front end forms and reports.  

    I've looked at the newly created forms and can't pin point any obvious issues.  I've tried to copy buttons that were created in the 2013 version and use them as a base and modify for the new but the file freezes for those as well.  

    Do I have to recreate my front end in 2016?  Or do I just have to continue to create new features in 2013 but can still use 2016 to collect the data?

    Let me know if you need any more information or background.

    Wednesday, December 14, 2016 2:04 AM

All replies

  • You always do your development using the oldest version of Access you will be using, so in your case Access 2013.

    "when testing the new buttons the database freezes"

    What do the buttons do?  Can you post the macro/code?
    Do you receive any error messages?
    Does your VBA project compile without errors?
    Have you Compacted the Db?
    What is the file size of the Front-end and Back-end?


    Daniel Pineault, 2010-2016 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net


    Wednesday, December 14, 2016 2:19 AM
  • I've heard about that "developing using the oldest version".  So I guess that just means that any changes I want to make will have to be made in 2013?

    The buttons are macro's and they just simply open other forms.  I don't receive any errors it just freezes.  And it's only on the newly created forms and buttons.  So I would assume that it's the created in 2013 issue and just go back to making any modifications int he 2013 and that should fix that.

    Again somewhat of a beginner so I don't have any VBA that I have added.  Everything is just in macros so not sure about compile without errors.

    I have compacted the DB but that was by mistake because as you know it's compacted / fix errors or something like that and I was trying to figure out ways to find the errors and fix them.....with this specific error/problem.

    I'm responding through my tablet so I do'nt have the file in front of me but I believe the front end is somewhere around 3500kb and the backend is pretty small because I deleted most of the test data since we were just releasing it and this error came up and caused us to stop doing anything with it till it was fixed.

    Question:  If everyone that will use this database is on 2016 could I recreate the front end in 2016, link the 2013 backend, and go forward with that or would I have to recreate the backend in 2016 as well and just start fresh?  In reality it wouldn't take that long to do but just a pain.  Just trying to limit the amount of rework.

    Thanks,

    Tony

    Wednesday, December 14, 2016 3:13 AM
  • You don't need to recreate anything in 2016 for it to work in 2016.

    Your file sizes are not an issue, I was just checking that you weren't nearing the 2GB limit and you obviously are not.

    Since you don't have any VBA disregard the Compile question.

    Does the issue always happen with the same button?  If so, could you post the Macro?

    Is your network between your BE and FE slow?
    Are you on a wireless network?  This is a no-no with Access.
    Do you establish a persistent connection at the startup of your db between the FE and BE?
    For fun, as a test, open any table in your db when you open the FE and then try using one of the buttons that normally freezes your application.


    Daniel Pineault, 2010-2016 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net


    Wednesday, December 14, 2016 3:24 AM
  • It has only been happening with new forms that I created in 2016 and new buttons.  I tried adding a picture of the macro but the site isn't letting me add pictures....read below though because it doesn't matter.

    I just did a test that I added a new button to an existing form and it worked without any problems.  So it must be the new form that I created.

    I also did the test that you mentioned above.  I had the BE open with a table open and tried the button and it worked without freezing.  Then I closed the table and tried the button again and it worked again without freezing.  So then I closed the BE and tried the button and it worked again without freezing.  Then I realized what happened...I typically use three monitors but when I've been testing the FE I'm usually just on one monitor for some reason.  What is happening is the form that is opening is opening on another monitor....it's not plugged in so I don't know that but I also can't do anything because that form that is open somewhere else.  So if I'm on one or three monitors how do I tell the database to only use the current screen?

    Also, I am doing the no-no...we are primarily on a wireless network and we do the majority of our work through dropbox.  So not sure how much that's going to screw things up.

    Wednesday, December 14, 2016 3:11 PM
  • "Also, I am doing the no-no...we are primarily on a wireless network and we do the majority of our work through dropbox.  So not sure how much that's going to screw things up"

    You are doing the 2 biggest no-nos for an Access database:

    • using wireless
    • using it over a WAN

    this will lead to continuous headaches, but more importantly can lead to corruption.

    See http://www.devhut.net/2016/09/24/access-back-end-location-wan-online-server-onedrive-dropbox/ for more information on the above.

     

    I'd also urge you to setup a persistent connection at the startup of your db, see http://www.devhut.net/2012/09/29/ms-access-persistent-connection-in-a-split-database/ for the details.


    Daniel Pineault, 2010-2016 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net


    Wednesday, December 14, 2016 3:39 PM
  • Okay.  So I'll have to figure out where to go with the database because of the wireless network.  But, do you know how to have Microsoft know which monitor is my primary?
    Wednesday, December 14, 2016 6:31 PM