Man it seems like the company just went to 2010.........
I have a lot of programs in 2010 and just last week a user for a new program had 2013 and the program did not load correctly.
This is going to start to become a real issue and I want to try and get ahead of it now.
I'm sure there are plenty of other people that have had to do this already. Any suggestions?
My plan of action (that I'm making up as I go) so far is:
Get a second computer so I can run both 2010 and 2013.
Make a copy of all the front ends and convert them to 2013.
Hopefully I can make both the 2010 and the 2013 front ends talk to just one back end. I don't know if this possible yet.
Also I want to put in some code when a program loads up to see what version of Access they have and if they have the wrong one, tell them to get with me for an updated version. Can that be done?
I'll just run both versions until the mandatory upgrade date.
This seems like the best plan of attack for now.
Any suggestions?
I have a lot of programs in 2010 and just last week a user for a new program had 2013 and the program did not load correctly.
This is going to start to become a real issue and I want to try and get ahead of it now.
I'm sure there are plenty of other people that have had to do this already. Any suggestions?
My plan of action (that I'm making up as I go) so far is:
Get a second computer so I can run both 2010 and 2013.
Make a copy of all the front ends and convert them to 2013.
Hopefully I can make both the 2010 and the 2013 front ends talk to just one back end. I don't know if this possible yet.
Also I want to put in some code when a program loads up to see what version of Access they have and if they have the wrong one, tell them to get with me for an updated version. Can that be done?
I'll just run both versions until the mandatory upgrade date.
This seems like the best plan of attack for now.
Any suggestions?