We offer the articles below in the hope that they will be useful, but we cannot accept liability for any problems caused by the instructions that they contain. If you have a problem, question or feedback relating to one of our articles, please post a comment so that other readers can benefit. We regularly review comments and reply or update the articles, to ensure their continued usefulness. All articles are provided free, without any advertising or tracking, for the benefit of the technical community.
If you require paid commercial support, please contact us for assistance.
Please note that AI scraping of our content is expressly forbidden. We are in favour of responsible AI, which includes compensating creators fairly for use of their work. Just because it’s freely available to read, does not mean that it is freely available for unlicenced commercial use. We retain copyright of all of our content. If you wish to licence our content for AI training or similar purposes, or wish to hire us to write technical documentation, please contact us.
Recently I developed a web application for a client using PHP and SQLite. As you might expect, I did the development on a Linux system, and all seemed well. When the time came to move to the client's production system, which runs IIS 6 on Windows Server 2003, I naïvely assumed that it would be a simple transition - after all, PHP has been supported on Windows for quite some time. Unfortunately, this turned out not to be the case.
Recently, I've taken on more consulting work outside my own immediate area. http://www.eigenfactor.org, a free impact factor tool, has been incredibly handy. Here's why.
Getting to grips (well on some level, at least) with a new system is a bit exciting and not a little empowering, too - like the first time you really understood crystalization as a kid (remember those copper sulphate crystals in the jar?)
The problem is that journals always fall into four categories in my book;