frustrating
Registered User.
- Local time
- Today, 03:50
- Joined
- Oct 18, 2012
- Messages
- 68
Hey everyone,
I have a database that was developed in 2010. I know there's a compatibility issues from developing in 2016 and having it be backwards compatible (object library 16 vs 14), but I thought things should be ok if it was developed in 2010 and viewed on 2016.
What I found is that the program worked correctly in 2016, but when viewed again in 2010, it was trying to use the 16 object library and I was getting errors.
Is there a way to support this? I mean, at the very least I could run two versions of the front end and check to see what version the user is using and route them to that particular front end, but is there a cleaner way?
Thank you so much for your help.
I have a database that was developed in 2010. I know there's a compatibility issues from developing in 2016 and having it be backwards compatible (object library 16 vs 14), but I thought things should be ok if it was developed in 2010 and viewed on 2016.
What I found is that the program worked correctly in 2016, but when viewed again in 2010, it was trying to use the 16 object library and I was getting errors.
Is there a way to support this? I mean, at the very least I could run two versions of the front end and check to see what version the user is using and route them to that particular front end, but is there a cleaner way?
Thank you so much for your help.