Is it possible to downgrade Access 2016 to Access 2013? Can I use the product key of Office 2016?
Is it possible to downgrade Access 2016 to Access 2013? Can I use the product key of Office 2016?
not so far as I am aware. If you explain why you want to downgrade, we may be able to suggest alternative strategies.
I bought a synchronization-tool (€ 1 000,00): DBSync for MS Access 2013 and lower. Some of my clients do have Office 2016 Pro, but it don't work with the DBSync. So I want them to downgrade to Office 2013 Pro.
My license of DBSync willend 31/12/2017, then I take the DBSync 2016.
can you not upgrade dbsync? Or talk to the guys at Redwood whether a downgrade is possible. It appears to be possible to buy 2013 licenses but don't know if the vendors are genuine.
I've heard of but not familiar with dbsync so not sure whether your issue is backend table related (in which case I would have thought it would not be a problem since the .accdb is likely to be the same) or front end related - i.e. using vba code to run dbsync functions which in turn rely on earlier library versions. Also is it possible the issue is a 32/64 bit issue?
That's just the problem. Upgrading DBSync 2013 to the most recent version (2016) = again about € 1 000,00 for this upgrade. So I want to downgrade my clients from MS Office 2016 Pro to MS Office 2013 Pro. (They already paid the Office 2016, so why not the possibility to downgrade ?)
As I suggested - talk to Microsoft, I don't know whether it is possible or not.so why not the possibility to downgrade ?
With regards dbsync, I struggle to believe a company ties its license in such a restrictive way that later versions of the software it connects to cannot use it without some sort of sensible upgrade path. There is very little difference between access 2016 and 2013, mainly cosmetic.
And did you consider my other suggestions?
As a matter of fact ,my issue us backend table related. There is no VBA-code in my backend.accdb (VBA-code only in my frontend.accdb)
I forgot : I'm working with the 32-bit MS Office.
so is that the reason why, or is there still an issue?
I tried to install 'Access Runtime 2013' together with the 'MS Office 2016 Pro' and now DBSync is finally working fine .
Thanks a lot.
glad you found a solution. Didn't think of the runtime version, good call.
But just out of curiosity, if you have two full versions of access, what happens when users switch between the two is it takes a few moments, sometimes a lot longer for windows to swap out the 'old' version and swap in the 'new'. Does this not happen if one of the versions is runtime?
With 2 full versions installed together (2013 and 2016) DBSync is running fine.