OpenAI advertising measurement

    Allow OpenAI to measure page views and completed contact requests, including a hashed email address and, when available, a hashed customer ID from your contact record for matching? The contact form works either way. Your choice applies only to OpenAI advertising measurement. Privacy notice

    Change this choice any time using Advertising measurement settings in the footer.

    Emergency TriageExperiencing system crashes, corrupted TPS files, or sudden developer departure?
    Back to Blog
    Clarion Maintenance

    Clarion Software Support: What to Look For Before You Choose a Provider

    Clarion Software Support: What to Look For Before You Choose a Provider

    Your Clarion application probably does one of the jobs your business cannot do without: taking orders, billing customers, tracking stock, running a clinic or a production floor. When something goes wrong with it, the question is not academic. Who do you call? Good Clarion software support means having a real answer to that question before the problem arrives.

    This guide is for owners and IT managers who are responsible for a Clarion or SoftVelocity system and need to decide how to support it. It explains what support should cover, what to ask a provider, and how a sensible first engagement works.

    Why Clarion software support is a different job from general IT support

    Your IT team or managed service provider keeps the network, the workstations and the servers healthy. That work matters, but it usually stops at the edge of the application. A Clarion program is custom software with its own data files, its own build process and often decades of business rules written into the code. Fixing it takes someone who can open the source, read it and change it safely.

    That is why a general help desk can restart a server but cannot tell you why an invoice total is wrong after a Windows update. Clarion software support sits at the application layer, and it needs people who know the language, the templates and the data drivers your program was built with.

    What good Clarion software support should cover

    • Fixing faults. Crashes, error messages, reports that print the wrong figures, screens that freeze. Someone needs to reproduce the problem, find the cause and correct it in the source.
    • Small changes. A new field, a changed tax rule, an extra report. These requests are constant in a living business system.
    • Keeping up with the environment. New operating systems, printers, network changes and security settings can all upset an older application.
    • Protecting what you have. Source code, data dictionary and build settings need to be located, backed up and understood, so one lost laptop does not end your ability to change the program.
    • Knowledge of your business rules. The calculations and exceptions in the code are the real value of the system. Support should treat them with care and write them down as the work goes on.
    • A path forward. When the time comes to add a web portal, connect another system or plan a move off older technology, your support provider should be able to advise, without pushing you toward a rewrite you do not need.

    Break-fix, ongoing and advisory support

    Most arrangements fall into one of three shapes, and many businesses use a mix.

    Break-fix

    You contact someone when something breaks. This suits small, stable systems, but you are looking for a provider in the middle of a crisis, which is the worst time to learn how a system works.

    Ongoing support

    A provider who already knows your application is available as needs arise. The advantage is familiarity. They have seen your code, so a problem on a busy Monday does not begin with a week of discovery.

    Advisory support

    Some businesses mainly need an experienced opinion: is this a bug or a data problem, is it safe to upgrade this machine, can this feature be added without breaking month-end. A short conversation with someone who has worked with Clarion for years can save a lot of guesswork.

    Questions to ask a Clarion support provider

    1. How long have you worked with Clarion, and with which versions? Your program may have been built in an older release. Ask whether they have worked with that generation, and with both ABC and legacy templates if your application uses them.
    2. Can you work from our source code, and what happens if we cannot find it? A provider should be able to explain what they need and how they handle the situation when only the compiled program remains.
    3. How do you make changes safely? Look for answers about working on a copy, testing before anything goes live and a way to roll back.
    4. What will you document? Notes on how the system is built and the business rules inside it should stay with you, not in one person's head.
    5. How do we reach you when something is urgent? Agree this before you need it.
    6. Will you tell us when a rewrite is not necessary? A provider with a strong preference for replacing everything is selling something other than support.

    How a first engagement should work: stabilize first

    At Clarion Programming Help we have been working with Clarion for 30 years, and our approach to support starts the same way every time: stabilize first. Before changing features or planning anything ambitious, we want the system running reliably and the essentials secured.

    1. Understand the situation. What is failing, how it affects the business and how urgent it is.
    2. Locate and protect the essentials. Source files, data dictionary, build setup and a current backup.
    3. Fix what is hurting the business. Deal with the most disruptive problem first, with changes tested before they reach your users.
    4. Preserve the business rules. Record how the program behaves so future changes do not undo years of accumulated logic.
    5. Decide what comes next. Continued support, an integration with a modern tool, or a phased plan for modernizing, always at a pace your business can handle.

    When to get Clarion software support in place

    The best time is before a crisis. Consider setting it up now if any of these apply:

    • The original developer has retired, moved on or stopped responding.
    • Only one person knows how the system works.
    • You are not sure where the source code is.
    • The program has started crashing, or behaves oddly after a Windows or hardware change.
    • You want a web portal, mobile access or another system connected to your Clarion data.

    Talk to us about your Clarion system

    If you are looking for Clarion software support, the simplest next step is a conversation about your situation. Tell us what the application does, what is going wrong or what you want to prepare for, and we will give you a practical view of where to start. Contact us to get in touch.