CODEWITHSUNDEEP
ms-accessms-access-2010ms-access-2013
Tyler R
Tyler R

Reputation: 504

MS Access 2010/2013 Transition Issues

So currently my boss and I are the two employees that work on our company's access database. I just got Office 2013 on my computer and he is will working with 2010. We have ran into some inexplicable bugs with the database.

Most of these can be fixed by just copying an old version of a form or report into the database when it fails; however, it is quite disconcerting when we spend hours trying to discover why something is wrong and are able to fix it without explaining why.

Most of the issues so far have occurred when I am using the db in Access 2013. So far the issues have been:

I guess my question is if anyone else has had issues along these lines, or if they knew of any other known issues. I tried to research errors people have been having, but I couldn't find anything besides Microsoft's official release of what features were being deleted.

As always, thanks in advance!

Upvotes: 0

Views: 905

Answers (2)

AVG
AVG

Reputation: 1462

Your system should be split into two files. FE(front end) containing all forms, queries, code, etc., linked to the BE. BE(back end) containing the data tables only. Maintain a development copy of the FE that is only used for making modifications. Each user should have their own copy of the FE on their local machine. If you don't know how to split, just search for it as there are plenty of instructions out there.

Upvotes: 2

kismert
kismert

Reputation: 1692

I have 2010, but I worked with a consultant who worked on the same project in 2013. I too, saw some behavior that looked like version related bugs, but nothing definite.

Responding to your list:

  • Access occasionally crashes and restarts when I am working in the VB code -- This has happened to me in every version of Access I have used, from 97 to 2010.
  • Some forms bug out for no reason. It yet again occurs when I am working in the VB code if there is a compile error... -- If the compile error is severe enough to lose project state, this is not surprising.

Recommendations:

  1. Decompile your application front-end occasionally, especially when 'weird' errors show up. See this SO link: automating decompile / recompile in ms-access
  2. Compact & Repair at least daily while developing your application
  3. Backup! Do this at least for every significant revision. Sometimes, the Access front-end will become so corrupt that it trashes all of your work. When this happens, nothing is recoverable.

Upvotes: 1

Related Questions