Please post Access questions at
http://www.accessforums.net/. Before anyone can help resolve this issue, you'll have to provide a whole lot more detail than you have here - probably including the code behind the form concerned and specific details of what the supposed bug is.
That said,
if the issue is a bug in Access 2010 (it may instead be a bug in the developer's code), there is no guarantee it will be fixed in Access 2013. Equally, MS might release an Access 2010 patch that fixes it. None of us here can see into the future.