Author Archive: David Musgrave
Following on from my previous posts: Customising the Company Login window series Part 1 – Introduction , Customising the Company Login window series Part 2 – Visual Basic for Applications and Customising the Company Login window series Part 3 – Dexterity , here is a discussion about trying to create a solution using Visual Studio Tools.
After the successes of the All Saints College teams at the RoboCup Junior Australia 2014 WA State Championships , it went without saying that we would take our best teams to the National Competition in Brisbane on the 27 th and 28 th September. We ended up taking our Senior Theatre (Pickle JAR Productions) and Senior Dance (The Inspector) teams as well as our top 2 Open Rescue (Sam and Me, Him & It) teams. Sadly neither of the CJs (Christopher Jack and Christopher John) were able to come due to other commitments
It has been a while since my last post. I have been very busy with a number of activities (more on that in a later post). One of those activities has been this year’s RoboCup Junior Australia competition. For the last two years I have been the mentor for the All Saints College Robotics Club.
It is time to release a new build of the Support Debugging Tool for Microsoft Dynamics GP for versions 10.0, GP 2010 (v11.0) and GP 2013 (v12.0). Build 19 primarily improves support for Microsoft Dynamics GP 2013 R2 as well as including some fixes and enhancements to existing features
How to Fix a Setup File is from a later version Error from the Support Debugging Tool when doing a Test Upgrade
This post revisits the issue previously discussed in the blog post: How to Fix a Setup File is from a later version Error from the Support Debugging Tool . The issue is that you receive the error message below from the Support Debugging Tool just after logging into Microsoft Dynamics GP: Setup File is from a later version (##.##.####) than the version (##.##.####) of the Support Debugging Tool on this workstation. Please check with your administrator if the correct location for the Debugger.xml setup file is being used