When Dexterity was first implemented on SQL Server for version 3.15, there was a number of decisions made on how to map the datatypes, fields and tables designed for ISAM platforms such as Ctree and Btrieve/Pervasive SQL to work on SQL Server.
One of the decisions was how to map the individual date and time control types to work with the datetime datatype in SQL Server.
Hey Developers… Are you attending the GPUG Summit 2017 conference in Nashville, Tennessee in October? If so, this article is to let you know about Microsoft Dynamics GP related Developer content at the conference.
I asked why there was not much content for developers at GPUG Summit and I was told that there are not many developers in attendance. I disagreed and requested a session for Developers, which Bob McAdam promptly organised … thanks Bob. 🙂
This article has been a long time coming and is the first of a series of articles on how I set up my machine for developing Dexterity applications across multiple versions.
I promised I would detail how my system is set up a while back at the reImagine 2015 conference and had never got around to writing the article until now.
In case you missed it, yesterday was Fabrikam Day for the Microsoft Dynamics GP community. This was the 12th April 2017, the date that the sample company’s, Fabrikam, data is based around.
For more information about Fabrikam Day and the sample company have a look at my article from yesterday:
While working hard yesterday I came across a post shared on the Book of Face by my friend Denni Conner. It showed the mathematic constant of π (Pi) played as a song and was an interesting approach to try and memorize the sequence of numbers.
The post said it was Pi Day because the date was 3.14 and that the celebrated time was 1:59 PM as that gave the number sequence 3.14159 which is Pi to 5 decimal places and the most that “normal” people can remember. If you can remember more digits that is great, but you are in a minority.
Last week, I wrote about a situation which was causing issues with the Database Validation feature of GP Power Tools. Triggers on the ACTIVITY table that fired when records are deleted that attempt to clean up data in the company that the record is related to.
The problem is that if the current user does not have access to this company or company database does not exist or is not online, errors are generated and the code fails. This is discussed in my blog:
Microsoft Dynamics GP 2015 R2 added lots of new features and enhancements and fixed a number of bugs too. However, it also introduced a change that is now causing errors in some ISV’s (Independent Software Vendor) products.
I first came across this issue when preparing to release GP Power Tools build 22 and was testing the Database Validation feature on my Microsoft Dynamics GP 2016 install.