[AccessD] Version Issue ?

[Jim Dettman]

Windows is not a problem, it's still 32 bit office, but personally I'd be leery of using 2013 and handing it to someone with 2007.  The desktop side has been fairly static,  but 2010 had a number of issues at release dropping back to 2007.   2013 is also the release that dropped a lot of desktop features, like ADP's.

Best particle has been to always develop in the lowest version you'll be distributing to.   References will be a problem right off.  2013 will auto update them when you open the db,  then the db will break when you hand it to a 2007 user.

Jim

Sent from my iPhone

> On May 16, 2016, at 5:42 PM, Brad Marks <bradm at blackforestltd.com> wrote:
> 
> All,
> 
> In the past, I have been doing my development with an older PC running Windows XP and Microsoft Access 2007.
> 
> A few months ago, I convinced management that I needed a new PC with Windows-7.
> 
> I am now starting to develop with Access 2013 (32 bit) on the new PC with Windows-7 64-bit.
> 
> The catch is that my applications will be deployed on about 25 PCs.  All have Windows-7, some are 32-bit Windows, some are 64-bit Windows.
> 
> There are various versions of Access on the deployment PCs (2007, 2010, 2013, 2016).
> 
> If I am careful to not use any new features in Access 2013, will I be able to develop with Access 2013 on a PC that is running Windows-7 64 bit and then deploy on our PCs that are using Window-7 32 bit and Access 2007 (runtime).
> 
> Thanks,
> Brad  
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com