Just Say Why

Visit our website, Just-say-why.com.

This site was originally envisioned as a place to find political issues relating to the computer industry. However, as the US government systematically destroyed the US computer industry, the blog became about all things political as everything political is related to everything else political.

Just-Say-Why solicits input from authors of all political persuasions, but there is an obvious abundance of Liberals that post and visit the site. Still, everyone is invited.

You can find pages and posts on countless subjects but you will find discussions on Financial Issues, just plain Political Issues, and Religious Issues. What goes better with politics than religion?

You can find fact-finding topics such as the distortions from the Scheels advertisement or the Harold Estes letter to the president.

If you fancy the thought of putting your political or religious ideas in print, feel free to drop by and sign up as an author. Thick skin is a requirement. Be warned. 🙂

Internet Security

There is no shortage of things that need to be done to address the issues of Internet Security. Here, you can find information on Security Audits, Security Training, Incident Response, Defining Security Policies, and numerous Case Studies.

Internet Security is not an issue to be taken lightly, even for the home computer. If you need experienced, professional help with your computer security, give us a call or leave a reply to this post.


Visit our other sites, like StatesCasinos.com.

If you’re looking for information on land based casinos, StatesCasinos is a great resource for the information you seek.

You can find a listing of all hotel casinos on one page. Of course, who wants to look at a list of hundreds of casinos? So you can look up the casinos by City and casinos by State.

Right from the front page you can find casinos in Nevada, casinos in Mississippi, casinos in New Jersey, casinos in Las Vegas, casinos in Atlantic City, and oh so much more.

Once you’ve found the hotel casinos in your area of interest, the next step is to see the environment. There are links to entertainment at the gambling halls, a list of eateries, and information on the hotel accommodations. And, of course, it’s important to see what deals they’re offering. Next you might want to check out the weather and get yourself a map to the hotel casino. What’s next? Well, of course there are links to make your reservations.

All that is available at StatesCasinos.com.

This is another quality site designed and maintained by Access Technologies Computer Services

Medical Facility Grading

To grade and evaluate certain services provided to health care facilities, this client needed a data management system that intimately knew the services provided to each facility as well as the function of each employee at each facility.

Though the foundation for this product was already developed when we inherited the project, it lacked many crucial features needed to combine the distinct functions into a cohesive product.

This project was also developed using MS Visual Basic and runs on all 32-bit Windows systems.

Of all the enhancements we have added to this product, possibly the most important is one that you can’t even see. During the course of this product, we have added a bottom-up object oriented class library for dealing with the client’s customers, employees, and services. Adding, changing, and fixing anything about the product is now much faster, easier, and less error prone.

Languages: Visual Basic(VB)
Platforms: Windows

Mobile PC Programming – Review Software

This client has numerous supervisors who work in the field and score and review the work. Using clipboards and then entering the clipboard data into a PC was troublesome and error prone, not to mention oh so “last century”.

After investigating numerous handheld computers, we decided on the HP pocket PC running Windows CE and Windows Mobile.

This project started in the early days of Windows CE and we worked through and worked around many many MS bugs. Before the project was even finished, HP and MS quit supporting the original platform so we migrated to the latest products.

The first release of ADOCE was of typical MS quality and next to useless so we built all the data management through file support. Once the new release of the CE operating system was released and the ADOCE was fixed, things went more smoothly

The initial release of the product was ready for testing within 5 months.

Since multiple pocket PCs where being used by many supervisors, and many different copies of the PC based data management software could be running simultaneously, we needed systems for managing concurrent connections and keeping tack of which supervisors used which pocket PCs.

The client wanted the pocket PC product written in VB/CE since there are many VB programmers available for future maintenance and enhancements. The one drawback to using VB was the lack of icon support. In order to support corporate icons, the client is considering using a C/C++ wrapper.

Languages: Visual Basic (VB, VBCE), ADO, ADOCE
Platforms: Windows CE (WINCE), Pocket PC (PPC)

Office Management Software

This Financial Services client had special requirements for office software. Much of the existing data was being maintained in spreadsheets and it was time consuming and error prone to change data entry personnel.

This particular client had used Quickbooks in the past and hated being “nickel and dimed to death” so he opposed the suggestion of going with a packaged product. It’s probably just as well, since his office personnel required considerable training.

We produced custom software for this client using VBA under MS Access.

The software was completed with two weeks, but documentation and training took two more weeks.

The benefits to the client’s decision to go with custom software included cost and reliability. Modifications were always fast and inexpensive and he wasn’t always having to pay for upgrades and add-on services.

Languages: Visual Basic Applications (VBA), Access
Platforms: Windows

Extracting Insurance Quotes

With each passing year, we see new products and services delivered through the Internet. Insurance quotes have been online since 1995 but some insurance carriers are still reluctant to get onboard. This insurance carrier wanted us to use their PC quote engine to automatically display quotes online.

Knowing that this would not be the last time this task was requested, we realized that trying to get the data from the PC by screen-scrubbing was out of he questions. It seemed that each month when carriers delivered their PC quoters, something in the screen layout had changed. This would make extracting the data from the PC screen, unreliable.

We opted for interfacing with the insurance carriers’ PC product through DLL interfaces. This required writing C/C++ and Visual Basic code to talk to the carriers’ executables.

Once a request was received from the website, the PC would query the carrier’s PC quoter for the correct quotes. Then the data was transferred back to the client’s web server and displayed using Perl.

In the long run, the client was very happy with this decision. This approach still requires some frequent changes due to interface changes from the carriers, but the amount of change is minuscule compared to the GUI changes.

Languages: C/C++, Visual Basic (VB), Perl, COM
Platforms: Windows, SunOS, Web

Windows Fortran Interface Library

Many Fortran programmers need to access the Windows API without being stuck with a MS compiler. This client needed just such access and found that many others shared that need.

To make this work right, we needed to add a Windows-like control loop as well as many wrappers to the usual MS API functions.

Our goal during this project was to use as much Fortran as possible and only rely on C/C++ or Assembly Language wrappers when absolutely necessary.

Of course, this project also required close work with numerous Fortran compiler vendors as we were exercising parts of the language than hadn’t been tested thoroughly.

Languages: Fortran, C/C++, Assembly Language
Platforms: Windows

Web Content Management

Our client had a website with many hundreds of pages of HTML and dynamic content. Many of the pages had similar format but there were always enough differences to make the site look irregular. Furthermore, data entry personnel were responsible for much of the dynamic content which changed at a rate of around 200 page changes per month.

The website was hosted on a SunOS machine and managed remotely using SSH and FTP using Windows machines

Since the page irregularities were the paramount issue to the client, we tackled them first. The solution was to work with a graphic artist and come up with a standard page layout, complete with images, buttons, bullets, and navigation gifs. Then we produced a suite of tools to merge the content with the templates.

This merging process allowed us to completely separate the content from the page layout. This separation allowed us to produce a concept of page “skins” that we could change at will with minimal work from the regular HTML programmers.

Most of the dynamic pages were produced with Perl CGI programs so they were converted to use the templates as well.

The next step was to deal with the content produced and maintained by the data entry personnel. This was a bit trickier since these employees didn’t know much about HTML and had even less interest in learning. The solution here was to produce a few more tools for the suite that formatted new HTML pages whenever the data entry personnel updated the content in the database. This required having select fields for the data entry personnel, such as “header”, “subject”, “date”…

Obviously, this new data-driven layout greatly enhanced the usability of the client’s data and allowed them to leverage their data entry employees better by producing more content with easier data maintenance.

Languages: HTML, Perl, Java, Javascript, CGI
Platforms: Windows, SunOS, SSH, FTP

Mainframe Fortran Language System

This project involved substantial modifications to an existing Fortran compiler, bringing it up from F77 standards to F90 standards. Since the ANSI Standards parsing requirements were so radically different, the entire parsing mechanism was rebuilt.

The core of this system relied on an intermediate language (IL) designed specifically for writing compilers. The IL was written in Assembly Language as were many of the Runtime Library routines

Since the client was located on the east coast, most of the works was dome remotely using TCP/IP file transfer tools as well as diff and merge tools.

This project also involved creating and maintaining a set of version control project files.

Languages: Fortran, Assembly Language, Intermediate Language
Platforms: GCOS, Honeywell