[AccessD] Version Issue ?

[James Button]

Brad,

Firstly - deployment on 32 bit win-7 from a 64 bit win-7 should - SHOULD not
cause any problems, if it is just a stand-alone app you are deploying  - the
run-time SHOULD be OK for the app
The Runtime facility needs to be the same 32/64 bit as the office app rather
than the windows .

Now - deployment to the various levels of Access means that the code you deploy
will need to be re-compiled on those versions of office 
DLL's and VB etc. need to match the Office version, and I believe there may well
be problems with the 2007 version. 
>From memory - Check for functions behaving differently such as when processing
empty variables.
 
Additionally, any code such as SQL for queries will need to be LATE BINDING in
order to have it use the code and DLL's etc. that are installed on the target
systems.

I would aim for Office 2010 code as a base level,  and hopefully, your 2007
knowledge will make the pain of  that upgrade relatively easy to cope with. 

You have not mentioned the likelihood of any, or all of those systems being
upgraded to Win-10, or web based app such as 365 or using Onedrive, etc.
There is also the process of distributing updates to the app. That could be
somewhat complicated as the users systems evolve - fixes, and new PC's 
I recently had some 'fun' with an Excel 2010 app - all based on a single
workbook with VBA code in it. 
Emailed the new version to users, and 1 user's system would not open the
workbook 
Resent with cc to a physically nearby user - and OK on the cc, but not on the
target system
Investigations of the system - fixes etc. located no differences
  
And - when the cc'd version was carried over using a USB stick - it worked 
Also saving the app workbook in 2003 mode shipping it via email and then having
the user re-convert it to their 2010 office gave them a working app.

Since then a further revision of the workbook was still reported as damaged and
unrecoverable - but the 2003  (.xls) version worked after being saved by 2010 as
a .xlsm type file 

JimB  
   
   

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad
Marks
Sent: Monday, May 16, 2016 10:43 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Version Issue ?

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