Debug C++ Workshop MIS Program

@vano101

Hello I have over 25 years of experience with C++ programming it's quick and easy task to debug your program, I can complete quickly

@WOFZahid

Hi, Your situation is a classic one — clean build, wrong numbers. That usually points to one of a few suspects: silent integer/float truncation, off-by-one in accumulation loops, signed/unsigned mixups, rounding applied at the wrong stage, or stale data being reused between report runs. The fact that it shows up on "several screens" suggests a shared helper or a common data path, not isolated bugs. My approach: 1. Set up the project in Dev-C++ on Windows exactly as you have it, reproduce the wrong output against your sample inputs. 2. Trace the calculation pipeline backwards from the wrong figure to the source data — instrument with logging, not guesswork. 3. Fix only the internals. Public headers, class signatures, and call sites stay untouched. 4. Add small test fixtures around the corrected functions so you can re-verify yourself. 5. Deliver corrected files (or a patch), a changelog mapping each fix to the screen/report it affects, and notes on the tests. Compiles clean on -Wall -Wextra is non-negotiable on my end too. Before I quote a firm price, I'd want to see: - Rough size of the codebase (files / LOC). - Which specific screens or reports are off. - One or two sample inputs with the expected vs. actual output. Happy to do a quick review of the source under NDA if needed, then give you a fixed quote and timeline. 9+ years in backend / business systems, comfortable with legacy C++ on MinGW toolchains. Regards, Haleem

@ssquare489

As a seasoned software engineer with a focus on C++, I can confidently offer my services to address the debugging issues your Workshop MIS system is encountering. With strong proficiency in C++ and deep experience in working with codebases of diverse complexities, I have a knack for quickly detecting and mitigating logic flaws. Moreover, my familiarity with dev cpp on Windows will ensure a smooth development process. One of the distinct strengths that sets me apart is my rigorous approach to QA and testing. I understand that robustness is a non-negotiable attribute for your project. Deploying stringent processes, including compiling cleanly with ‑Wall ‑Wextra, and meticulous comparison of outputs against expected results, I make sure the code repairs I implement do not interrupt the existing operations or introduce new regressions; but deliver precise alignment.

@ELGAMLDev

Hey, Wrong output on a codebase that compiles cleanly that's a logic bug, not a build problem. Usually means one of three things: a calculation that's slightly off, a value that's being accumulated or reset at the wrong moment, or an edge case that only triggers with specific data combinations. I'm comfortable in Dev-C++ on Windows and I work with STL patterns regularly, so the environment isn't an issue. Here's how I'd approach it: get the code building on my end, then go through each broken screen with your sample inputs until I can reproduce the wrong figure. Once I can see it happening, tracing it back to the source is usually quick. I won't rewrite anything or change the interface just fix the internal logic that's producing the bad numbers. Deliverables are exactly what you listed: corrected files or patches and test case notes so you can verify it yourself. Compiles clean with -Wall -Wextra, no new warnings.

@efr2000020

Hello, I will fix the bugs and give you free tech support in case something goes wrong again. I am an experienced C++ developer with many years of experience in building complex and high performance applications. Regards,