By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,455 Members | 2,293 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,455 IT Pros & Developers. It's quick & easy.

Access 2013 Bugs (?)

100+
P: 101
I have been using Access 2013 (in Office 365) with Windows 8.1 for about a month and a half now. I was a little reluctant to switch from 2010 on Windows 7, but I figured I should try stay ahead of the curve, and I also heard it had much better functionality for touch screen devices which I imagine are only going to get more and more popular. I have noticed a few bugs so far that I was wondering if anyone else has seen or knows how to fix.
The worst one I have come across is that I keep getting an error message after I make even the most minor design changes (such as moving a control) saying that my object (the entire form or report) is in an unrecognizable database format and it can't be opened. It then tells me that I should re-import it from a backed up copy of the database as if all hope were lost for it. After that the object won't even open in 2010. These issues have all been forms or reports that I created on my old system and tried to modify in 2013. Luckily I keep a lot of backup files and I haven't lost a significant amount of work.
The second bug that I can think of right now is that when I open up a section in the navigation tab and try to scroll through the list, it keeps jumping up a bunch of records, but less and less each time. To get to the bottom of the list I need to scroll down and let it stop about 5 times which is incredibly annoying.
If anyone has any advice I would appreciate it. I still can't make up my mind whether I like 2013 or not. The blandness is a stark contrast to 2010 and in my opinion a poor UI. On the contrary I haven't really noticed many features that are great improvements. From what I've gathered Access 2010 was a very successful upgrade from all previous versions, but it was also the version I learned on so I don't know much about the previous releases.
Jan 15 '15 #1
Share this Question
Share on Google+
6 Replies


twinnyfo
Expert Mod 2.5K+
P: 3,031
GKJR,

In moving to 2013, you may have to create a new, blank database in 2013, then import all your tables and objects from your old DB. This sounds like a pain and it is. It may just solve your problem.

The true "solution" is for MS to make applications that like previous versions better than what they currently do.

Hope this hepps!
Feb 25 '15 #2

Expert 100+
P: 1,221
I have had a number of sudden crashes with Access 2013. I'm sure you know the kind, "Access has stopped working ..." It probably related to my stubbornness about keeping 2007 and 2010 on the same machine.

Jim
Feb 25 '15 #3

100+
P: 101
I finally gave up on Access 2013. I tried importing my objects into a new 2013 DB and I was still having the same issues. What really pushed me over the edge was that I ran into the same problem with my troublesome form where Access said it was in an unrecognized database format and it needed to create a back up of the file. When the backup was done it had deleted all of my forms. I tried reverting to one of my own older backups and it did the same thing to that file as well. I am dropping my subscription to Office 365 and reverting back to Office Pro 2010. I have enough problems trying to develop new components and learn new things to have to deal with this nonsense.
Mar 11 '15 #4

Stevan Bias
100+
P: 207
Personally I have had no issues going back and forth. I regularly work from home which I have Access 2013 and then move my project back to my work laptop and/or desktop which are both 2010 and have had no issues what so ever.
Mar 11 '15 #5

100+
P: 101
Stevan - do you have anything good to say about Access 2013, other than it works like you would expect it to? I didn't notice any significant improvements.

I think one of my issues is that the rest of my office - about 5 other users - as well as the back end file are all in Access 2010, but my front end file is in 2013. That shouldn't be an issue though. Is your database split and are other users or the back end file hosted in Access 2010?
Mar 11 '15 #6

Stevan Bias
100+
P: 207
The project I am currently working on isn't split yet (big yet). But currently significant improvement? No... Nothing useful has been made obviously to me yet.
Mar 12 '15 #7

Post your reply

Sign in to post your reply or Sign up for a free account.