Senior Expert Access/Excel/VBA/SQL Server Developer/Dot.Net Web/MVC/EF/Azure, Troubleshooter, Optimizer, UI Enhancements, etc...
I have 30+ years of experience working with Access, Excel, and then integrating them into a harmonious fluid application, whether it be for the Desktop, or on a WAN. I have developed using every version of Microsoft Office and SQL Server since inception.
I specialize in Finance and Manufacturing, including CRM, Inventory and Work Order Management, Job Costing, AR, AP, Purchasing and Sales Forecast Automation, etc. I feel those environments are structurally synonymous with most any other scenario. My current experience involves Loan Origination and Servicing.
Working in Finance and Manufacturing, I could not afford to make mistakes. My work ethic developed beginning with my father and being in the Military, in the field of Aviation, where a tiny mistake could cost lives. I am detail oriented with an eye for efficient user friendly complete, from the ground up, to the most custom application imaginable.
I have proven complex methods that are far more efficient than the conventional developer, regardless of how well they score on a test; I am the person that goes the extra mile(s) to adhere to the rules of development while maintaining a fluid user friendly interface. I develop from the ground up or customize pre-existing systems. Whether I am developing in Access or Excel, I always structure the data for easy possible future migration, regardless of the interface. An interface can be easily replicated, but carelessly stored data can be very costly. My interfaces are fluid and user friendly. They utilize as much as the available functionality permits, by using Drop-down and List Boxes, and applying Event Code to link to related data without having to return to a menu or dashboard.
I am extremely fluent in VBA, using various Object Models, i.e. Access, Excel, DAO, ADO, SQL, Class Modules, SQL Server T-SQL, Stored Procedures and Custom Functions and Triggers, SSMS, SSRS, and SSIS, etc. I write code that a lay person can understand. Where this is not possible, I comment the purpose and flow of the Code.
I do not implement limitations, as a lot of developers do, that force the Client to always call on the developer every time a little change is needed. I develop in such a way that considers future expansion. The only time I would ever need to be called upon is to implement new functionality. I prefer to teach Clients the basics so that they can make the subtle physical design changes to the interface that they want, without destroying the integrity of the system. Because I follow the rules of development, the system is straight forward and easily understood.
