file conversion. This may require minor manual adjustments. For example,
when VC++ 2013 converts the VS2008 project files, it changes the debug
build output directory from `debug` to `debug\x64` but fails to update
the linker settings for the executables.

MySQL++ still mostly works with Visual C++ 2003. The main exception is the [Specialized SQL Structures](doc/html/userman/ssqls.html) feature, which doesn’t work at all any more. It appears to be difficult to fix, because the symptom is that the compiler crashes when you try to build even the most trivial SSQLS code. There are [several possible ways](doc/html/userman/ssqls.html#ssqls-vc2003) to work around this limitation.

If you must use Visual C++ 2002 (a.k.a. 7.0) or older, you can try the [ancient 1.7.1 version](/#oldver) of MySQL++. This is a third-party contribution which is [known to have
If you must use Visual C++ 2002 (a.k.a. 7.0) or older, you can try the [ancient 1.7.1 version](/home/#oldver) of MySQL++. This is a third-party contribution which is [known to have
bugs](http://lists.mysql.com/plusplus/1069). You might be better off using [Connector/C](http://dev.mysql.com/downloads/connector/c/) instead.

The library’s primary maintainer only uses MySQL++ seriously on Linux, macOS and FreeBSD systems, and let his MSDN membership lapse years ago. Consequently, he only tests MySQL++ occasionally under the current version of [Visual C++
Community](https://www.visualstudio.com/vs/community/). Consequently, we’re highly reliant on testing and patches from the user base for this platform.

If you’re not using a recent version of Visual C++, you should really
consider upgrading as the compliance of the compiler has improved

package is fairly closely tied to the system it is built under, so it’s
possible that RPMs you build on your system will work better than those
built elsewhere.


## Nothing’s working at all! Is it broken?<a name="broken"></a>

Maybe, but have you tried running the examples? Follow the instructions in the `README-examples.txt` file. If the examples work but your program doesn’t, chances are good that the error is in your program; study the examples, and [read the manuals](doc/). If the examples also fail to work, post to the mailing list with a detailed failure report.
Maybe, but have you tried running the examples? Follow the instructions in the `README-examples.txt` file. If the examples work but your program doesn’t, chances are good that the error is in your program; study the examples, and [read the manuals](/wiki?name=Documentation). If the examples also fail to work, post to the mailing list with a detailed failure report.


## I’m sure I’ve found a bug. How do I submit a report?<a name="bugreport"></a>

We’ll want some code that demonstrates the bug. No doubt you’d rather not send us a copy of your database to demonstrate the problem, and to be frank, we don’t want your database, either. The best thing is to modify one of the MySQL++ examples so that it reproduces the problem you’re seeing. This lets the people that can help you reproduce the problem on their machines, without needing your database.

Once you have your problem boiled down to a simple example, send the source code to the mailing list along with a detailed report. We want to know what you expect the program to do, and what it actually does on your machine. Keep in mind, programs often behave differently on different systems. As a programmer yourself, you know what it is like to