Wednesday, October 15, 2014 After a jammed pack Academy Training day on the previous day, Summit Day 1 begins with a little stroll from my hotel down to the America’s Center Convention Complex . On the way there, I cannot help but to snap a picture of the now very famous Runner Fountain at Kiener Plaza, which happened to be running a pink to red tone in support of the Cardinals
Monday, October 13, 2014 Summit is now gone, but I wanted to take some time to recount some of the events as I saw them happening. First, I wanted to congratulate the Dynamic Partner Connections team for an excellent event hosted at the Renaissance Hotel.
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.
On my computers at home I have a backup and synchronization regime to ensure that each computer has access to the files I want (even when offline) and that there is no chance of losing any data in the event of a disaster. In this post, I will explain my regime and some of the tools and tricks I have learnt. While I am sure others will have their own systems and might not agree with what I am doing.
Last week, I resolved a rather bizarre case for a customer. The Situation Each time the customer’s SQL Server was restarted for whatever reason, only the ‘sa’ user was able to log into Microsoft Dynamics GP. Once the ‘sa’ user had logged into Microsoft Dynamics GP at least once, then all the other “normal” users could log in and everything was fine until the next time the SQL Server was restarted.
A while ago I had a case where the customer was storing data in the DUOS (Dynamic User Object Store) table from a VBA (Visual Basic for Applications) customisation.