Hi,
I support an Access 2010 dbase for a group of 18 users. It's a pretty simple dbase - a handful of tables with some forms, queries and reports built off them. There are no macros/code. The dbase has been around for 10+ years, and the users' needs are well-known. Support generally consists of changing a parameter in a query, which works out well for me as I'm not a programmer.
The dbase is split, with each user having a "local" copy of the front end on their home drive. I control the back end, which resides on a separate, shared drive.
We're getting ready to upgrade to Access 2013. I've actually used Access 2013 in a single user (non-split) environment and didn't encounter any problems, either with 2013 or in opening a 2010 dbase in 2013.
Does anyone have experience of migrating a split dbase into Access 2013? Any problems encountered? Any issues I should be aware of?
Thanks,
Lyn
I support an Access 2010 dbase for a group of 18 users. It's a pretty simple dbase - a handful of tables with some forms, queries and reports built off them. There are no macros/code. The dbase has been around for 10+ years, and the users' needs are well-known. Support generally consists of changing a parameter in a query, which works out well for me as I'm not a programmer.
The dbase is split, with each user having a "local" copy of the front end on their home drive. I control the back end, which resides on a separate, shared drive.
We're getting ready to upgrade to Access 2013. I've actually used Access 2013 in a single user (non-split) environment and didn't encounter any problems, either with 2013 or in opening a 2010 dbase in 2013.
Does anyone have experience of migrating a split dbase into Access 2013? Any problems encountered? Any issues I should be aware of?
Thanks,
Lyn
Migrating split 2010 dbase to 2013
