Fix Null Error In VB

I have a long-running Visual Basic application that functioned perfectly until I migrated its back-end from one SQL Server instance to another. The schema, tables, and data definitions remain unchanged, yet the moment the app points to the new SQL Server database it throws a null-reference error and halts. Point it back to the original database and everything works, so the fault lies somewhere in how the code interacts with this new connection.

Your task is to trace and eliminate that null error. I will supply the source code, the existing connection details, and access to both the old and new SQL Server databases so you can compare behaviour side by side. Once the fix is in place the program must compile and run without exceptions on the new database and continue to operate as it always has on the old one.

Deliverables
• Updated VB source with clear comments on any changes
• Confirmation the app reads and writes correctly against the new SQL Server instance, error-free
• A short note explaining what caused the null issue so I can avoid it in future

That’s all that stands between me and getting this decade-old tool fully operational again.