When choosing a developer for a programming project, what are the skills you look for? Access...C#...PHP...Windows Phone? I offer those as well as others as you can see below:
- Borland C
- Borland C++
- Corel Paradox
- Java (Android Studio)
- Microsoft Access
- Microsoft C#.NET
- Microsoft Visual Foxpro
- PHP with MySQL
Next, I would like to highlight some applications I have created with some of my skills listed above. These projects were made according to exact customer specifications. That's my advantage over so many other developers. I create programmed solutions from scratch tailored to your needs. Many of my competitors in this business will just offer you a software package they made for your general industry, perhaps with some minor alterations included. In other words, you are not getting exactly what you need for your business.
An industrial cleaning company in Cleveland needed a program made that would manage the jobs they did for their customers, which included schools, restaurants, and sports facilities. I created this in Microsoft Access. In addition to the module for keeping track of their industrial cleaning jobs, it also ran several reports that listed jobs using varying input criteria. It had a module for keeping track of quotes they made for bidding on different jobs. There was a very unique feature to this program. It temporarily suspended itself when it called up a Borland C language for DOS program I created that mass imported quotes that had already been made in Microsoft Word. The DOS program carefully navigated through the different aspects of each Microsoft Word quote and selectively fished out the needed information. That was then transfered into the Microsoft Access data table for cleaning job quotations. It was challenging, but ultimately successful.
A company in the northeast Ohio area that manufactured and sold electronic products all over the world needed an order entry and invoicing application designed in the Corel Paradox database software. The centerpiece of this system was a "bridge" between the order that was initially created by the customer service representatives and the invoice that was created later. I made a Paradox objectPAL program that generated a batch of the orders into invoices. In addition to time and labor savings from the order and invoicing side, it printed shipping cards and ran many different sales reports that manipulated the accumulated data. This revealed sales trends that assisted the company with making timely decisions about how the company was managed in the future.
Many years ago in the mid 1990s, I made a Borland C language for DOS program for a customer that distributed industrial furniture (shelving, racking, and lockers) for businesses. This was a fairly extensive system that included invoicing, back ordered invoicing, accounts payable, accounts receivable, general ledger, inventory and various reports that usually filtered the data through date range inputs. They still use this old DOS based system today. Recently, I redesigned their inventory module from the old DOS program using Microsoft C#.NET so it would create a paper trail of transactions that detailed how the current on hand inventory balance was calculated for each of their items. The old DOS inventory module did not create a paper trail. In addition to manual additions and subtractions, it also tied in to the old DOS invoicing and back ordered invoicing update and print modules. In fact, portions of these two older modules had to be redesigned in the Borland C language for DOS to accommodate the newer Microsoft C#.NET inventory module. This makes the older invoicing and back ordered invoicing update and print modules automatically adjust inventory on hand balances in the new inventory module at the time printing occurs. I have also redesigned the general ledger module of this old program in Microsoft C#.NET. It's much more comprehensive and versatile than the old DOS version. It does double entry posting using an idea the customer came up with. There are six double entry posting screens divided by transaction type: CR, CD, GL, J, PR, and ST. Each posting screen lets the user post debits and credits to various ledgers listed on the screen. The postings are held in "temporary counterpart ledgers" to the real ones. When you scroll to the bottom of each screen, you can verify that the debits equal the credits before clicking a button to post everything to the actual ledgers in the Chart Of Accounts system.