UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
 
   Reply to this topicStart new topic
> Upgrading To Access 2013 Or 2016, Access 2010    
 
   
baffled100
post Oct 10 2017, 10:56 AM
Post#1



Posts: 337
Joined: 10-December 12



Hi,

We have an Access 2010 database. We are about to upgrade to either Office 20103 or Office 2016, with Office 2016 being the preferred choice. However, I was looking for some input on issues I can expect using an Access 2010 database in Access 2016 and/or Access 2013. Would it be better to keep using Access 2010, and just upgrade the other Office programs? Is there anything I need to do to the 2010 database BEFORE using it in a later version of Access? I've read up on it on the web, but it's also nice to hear from others who may have had experiences they would like to share with or warn others about.

Thanks in advance!


Go to the top of the page
 
GroverParkGeorge
post Oct 10 2017, 11:11 AM
Post#2


UA Admin
Posts: 30,692
Joined: 20-June 02
From: Newcastle, WA


Unless there are some uncommon features in your accdb, the upgrade to either version is not likely to raise issues.

It's probably better to use the same versions of Office apps. Keep in mind that if you end up having users on different versions of Access, you may well experience problems. So plan to roll everyone at the same time, or make alternative preparations if you can't do that.

--------------------
Go to the top of the page
 
Minty
post Oct 10 2017, 11:19 AM
Post#3



Posts: 61
Joined: 5-July 16



I would personally stick to the 32 bit version of access.

Switching to the 64 bit version doesn't give much benefit but can lead to some code conversion problems.
Go to the top of the page
 
River59
post Oct 10 2017, 11:28 AM
Post#4



Posts: 1,273
Joined: 7-April 10
From: Detroit, MI


Depending on how complicated any loop statements are in 2010, know that Access 2016 seems to run 'faster'. We found our loops stopping every 30 records because it got ahead of itself. I used a DoEvents in the loops to 'slow' it down.

--------------------
Remember ... Armstrong, Aldrin and Collins flew to the moon and back with a computer system less complex than a modern, programmable toaster ...
Go to the top of the page
 
gemmathehusky
post Oct 10 2017, 11:40 AM
Post#5


UtterAccess VIP
Posts: 4,426
Joined: 5-June 07
From: UK


I saw references to a couple of unresolved A2016 issues last week

1. vertical scroll bar in continuous forms not working correctly
2. occasional (faulty) out of memory errors on some large queries.

I am not sure whether these are resolved or not.

--------------------
Dave (Male)

(Gemma was my dog)
Go to the top of the page
 
GroverParkGeorge
post Oct 10 2017, 11:45 AM
Post#6


UA Admin
Posts: 30,692
Joined: 20-June 02
From: Newcastle, WA


thumbdn.gif Not that I've seen so far.


--------------------
Go to the top of the page
 
DanielPineault
post Oct 10 2017, 12:31 PM
Post#7


UtterAccess VIP
Posts: 5,260
Joined: 30-June 11



2013 vs 2016, you tell me the difference! Same, same. There have been a series of updates and they all have introduced more issue in 2016 (solve one, break another), so for that reason alone, I'd say stay with 2013 x32.

If you do decide to go with 2016, you are going to need to stay on top of your updates and update channel!

--------------------
Daniel Pineault (2010-2017 Microsoft MVP)
Professional Help: http://www.cardaconsultants.com
Free MS Access Code, Tips, Tricks and Samples: http://www.devhut.net

* Design should never say "Look at me". It should always say "Look at this". -- David Craib
* A user interface is like a joke, if you have to explain it, it's not that good! -- Martin LeBlanc


All code samples, demonstration databases, links,... are provided 'AS IS' and are to be used at your own risk! Take the necessary steps to check, validate ...
Go to the top of the page
 
DanielPineault
post Oct 10 2017, 12:33 PM
Post#8


UtterAccess VIP
Posts: 5,260
Joined: 30-June 11



@gemmathehusky

Nope, not yet. Supposedly it is fixed in 1709, which is available to insiders only at this point. Hopefully soon. It's only been 2+ months now! crazy.gif

--------------------
Daniel Pineault (2010-2017 Microsoft MVP)
Professional Help: http://www.cardaconsultants.com
Free MS Access Code, Tips, Tricks and Samples: http://www.devhut.net

* Design should never say "Look at me". It should always say "Look at this". -- David Craib
* A user interface is like a joke, if you have to explain it, it's not that good! -- Martin LeBlanc


All code samples, demonstration databases, links,... are provided 'AS IS' and are to be used at your own risk! Take the necessary steps to check, validate ...
Go to the top of the page
 
baffled100
post Oct 10 2017, 03:14 PM
Post#9



Posts: 337
Joined: 10-December 12



Thank you all! This is exactly the type of feedback I was looking for! I was planning on just upgrading to 2013, but I've been using the other Office 2013 apps at home and I really don't like the window colors (or lack of) and I read that 2016 has a separate color for each app, which sounded really helpful and better on the eyes. I know that's a bit of a silly reason alone to upgrade, but that's how much I dislike 2013's windows colors!

Thanks so much!
Go to the top of the page
 
baffled100
post Oct 11 2017, 05:20 PM
Post#10



Posts: 337
Joined: 10-December 12



I found this on the web on a PC Mag review of Office 2016:

"And the Access database app is still included for those who like to build custom data-driven applications, but it hasn't been updated since the 2013 version."
Go to the top of the page
 
GroverParkGeorge
post Oct 11 2017, 05:24 PM
Post#11


UA Admin
Posts: 30,692
Joined: 20-June 02
From: Newcastle, WA


Seriously? I wish people would do a bit of investigating before writing their opinions.

While it's true that the changes are relatively minor, it's simply not true that there have been no updates and enhancements as found on the MS Access blog. thumbup.gif

--------------------
Go to the top of the page
 
DanielPineault
post Oct 11 2017, 07:16 PM
Post#12


UtterAccess VIP
Posts: 5,260
Joined: 30-June 11



Strictly speaking the PC Mag quote is false, but at the same time, the 2 versions are so similar that it was recommended to use the 2013 runtime for a year or so while we all waited for MS to release the 2016 runtime! So while not technically true, I wouldn't say they are wrong.

Then again, IMNSHO, as I've stated many times before, that for the average user, there has not been any truly major advances in Access in multiple versions (yes I'm going to get roasted for this statement, but I stand by it). The ribbon was a waste, attachments, MVF, ... more often than not get users into trouble rather than help. Heck in newer versions MS has been taking things away, package wizard, Pivot table/charts, dbf file support, Treeview Control, Web Databases, Web Apps ... That all said, MS seems to finally be back investing in Access, so I'm hoping Access 2019 will bring us some new useful features, but time will tell.

--------------------
Daniel Pineault (2010-2017 Microsoft MVP)
Professional Help: http://www.cardaconsultants.com
Free MS Access Code, Tips, Tricks and Samples: http://www.devhut.net

* Design should never say "Look at me". It should always say "Look at this". -- David Craib
* A user interface is like a joke, if you have to explain it, it's not that good! -- Martin LeBlanc


All code samples, demonstration databases, links,... are provided 'AS IS' and are to be used at your own risk! Take the necessary steps to check, validate ...
Go to the top of the page
 
GroverParkGeorge
post Oct 12 2017, 08:35 AM
Post#13


UA Admin
Posts: 30,692
Joined: 20-June 02
From: Newcastle, WA


Referring to the link I posted, Daniel, MS did restore dbf support to Access 2016. That occurred because of feedback from myself and other MVPs and from the user community who rely on that ability. We used Access User Voice to let MS know about the problem. And, to their credit, they responded positively. Other enhancements have not been so significant, IMO, but they are being made.

I agree, and have previously stated, that the differences between 2013 and 2016 are relatively minor and largely what I think of as cosmetic, i.e. color schemes and changes to ribbon layouts. That, along with the on-going pattern of bugs--minor and major--creeping into 2016, suggests Access 2013 would be a good choice.

--------------------
Go to the top of the page
 
DanielPineault
post Oct 12 2017, 09:12 AM
Post#14


UtterAccess VIP
Posts: 5,260
Joined: 30-June 11



The biggest problems is that they often only half implement things: Nav Pane groups, themes, image gallery, ... where they add a new feature, but they are so complex that no one uses it, no one knows how!

As for dbf, returning a feature they removed isn't moving a product forward, it's restoring it to what it always was and if you review https://access.uservoice.com/forums/319956-...atus_id=1667463 you'll notice that the implemented items are almost all bug fixes, not actual new requests. Furthermore, the voting weight of those items are dismal next to the vast majority of requests that are ignored, not planned ... So at the end of the day, I truly don't see the point of the site as they are clearly not valuing the votes being made by their user base.

Anyways, I'm stopping here because I'm hijacking this thread which isn't fair to River59Baffled100. Maybe this one should be move to the chat forum where it could get hashed out.

I guess I'm the half-empty guy, and you're the half-full guy! At least together we have a full glass! hat_tip.gif

--------------------
Daniel Pineault (2010-2017 Microsoft MVP)
Professional Help: http://www.cardaconsultants.com
Free MS Access Code, Tips, Tricks and Samples: http://www.devhut.net

* Design should never say "Look at me". It should always say "Look at this". -- David Craib
* A user interface is like a joke, if you have to explain it, it's not that good! -- Martin LeBlanc


All code samples, demonstration databases, links,... are provided 'AS IS' and are to be used at your own risk! Take the necessary steps to check, validate ...
Go to the top of the page
 
River59
post Oct 12 2017, 09:36 AM
Post#15



Posts: 1,273
Joined: 7-April 10
From: Detroit, MI


Actually, Daniel, it was Baffled100 who started the post. I just chimed in with a heads up on the speed issue.

--------------------
Remember ... Armstrong, Aldrin and Collins flew to the moon and back with a computer system less complex than a modern, programmable toaster ...
Go to the top of the page
 
DanielPineault
post Oct 12 2017, 09:56 AM
Post#16


UtterAccess VIP
Posts: 5,260
Joined: 30-June 11



thumbup.gif Corrected.

--------------------
Daniel Pineault (2010-2017 Microsoft MVP)
Professional Help: http://www.cardaconsultants.com
Free MS Access Code, Tips, Tricks and Samples: http://www.devhut.net

* Design should never say "Look at me". It should always say "Look at this". -- David Craib
* A user interface is like a joke, if you have to explain it, it's not that good! -- Martin LeBlanc


All code samples, demonstration databases, links,... are provided 'AS IS' and are to be used at your own risk! Take the necessary steps to check, validate ...
Go to the top of the page
 
baffled100
post Oct 12 2017, 01:22 PM
Post#17



Posts: 337
Joined: 10-December 12



Oh, I was bothered at all and I find it all to be helpful! Unfortunately, I think since the only app that would be holding us back from upgrading to Office 2016 would be Access (because of the bugs that I am afraid of encountering now), for the sake of the staff's eyesight, I think we need to go to 2016. Is there a list of unresolved Access 2016 bugs that is kept up to date and is not too technical? Perhaps the bugs that are out there wouldn't even affect us.....

Thanks so much!
Go to the top of the page
 
DanielPineault
post Oct 12 2017, 01:41 PM
Post#18


UtterAccess VIP
Posts: 5,260
Joined: 30-June 11



Oh the latest bug is truly annoying, the scrollbars don't work in continuous forms!

You can look at:

https://support.office.com/en-us/article/Fi...en-US&ad=US
https://support.office.com/en-us/article/Fi...en-US&ad=US

This assumes MS actually keep the pages up-to-date.

I try to keep a list on my blog, when I'm aware of them, see: http://www.devhut.net/

--------------------
Daniel Pineault (2010-2017 Microsoft MVP)
Professional Help: http://www.cardaconsultants.com
Free MS Access Code, Tips, Tricks and Samples: http://www.devhut.net

* Design should never say "Look at me". It should always say "Look at this". -- David Craib
* A user interface is like a joke, if you have to explain it, it's not that good! -- Martin LeBlanc


All code samples, demonstration databases, links,... are provided 'AS IS' and are to be used at your own risk! Take the necessary steps to check, validate ...
Go to the top of the page
 
gemmathehusky
post Oct 13 2017, 06:15 AM
Post#19


UtterAccess VIP
Posts: 4,426
Joined: 5-June 07
From: UK


Out of interest, I am trying very hard to avoid upgrading my O365 to the 2016 version, because of the problems mentioned in this thread.
The latest message offering the update just changed. It no longer offered me a choice of "later" although I could just close the message.

for what it's worth, I thought A97 had everything in place pretty much. In the end you were forced to update to A2003 (because of windows issues), which isn't that dissimilar, and does add a few nice touches. It's much the same with A2007 (best avoided IMO), A2010 and A2013 (both equally useable. I dislike the ribbon, and I dislike the navigation pane, although the search bar is useful)

I actually still develop inA2003, and the mde's it generates run fine in all later versions.


--------------------
Dave (Male)

(Gemma was my dog)
Go to the top of the page
 


Custom Search
RSSSearch   Top   Lo-Fi    17th October 2017 - 06:14 AM