[Uleat]

You should be able to use the current SVN for both the server code and the database with no foreseeable issues.

Occasionally, a bug will slip in, but that is not the intended design...


In starting a new server with the current revisions (eqemu 2171 and 63 for peqdb) you just need to make sure that
you have all of the sql updates applied.

Note that the name of the peqdb is called peqdb_rev2142.sql and this was updated from peqdb_rev2133.sql in peqdb
revision 62.

The name of the database sql file ONLY reflects the cumulative changes to the database to match the eqemulator
revision and not the peqdb revision itself.


To keep current, you need to not only source in the database, but also ANY patches that equal or exceed the server
revision that you plan to run.


If you look in two places, you will find sql update files that need to be sourced in as well.

First, look in your peqdatabase (source) directory and you will see a folder called updates. Inside of this is a file called
rev2142.sql. This is a patch from the PEQ people that needs to be sourced in after the base peqdb_rev2142.sql file.

Once a new peqdb is released, you no longer have to apply anything older than the revision in the db filename.

Second, look in your eqemuserver\utils\sql\svn (source) directory. In here you will see several sql files that are
higher than the peqdb base file. You will need to source these in as well.

If you are running a revision that is less than the some of the sql updates, you may or may not run into issues by
sourcing in higher files than your server revision, so I'd only recommend sourcing in up to or equal to your actual eqemu
revision. Saying which server revisions work with what peqdb revisions is not exactly easy to say.

(If you're going to use server rev 2099, you should probably revert your peqdb back to something 2099 or less as well
and source in any updates to match. Thing is, you'll miss anything that has been updated/fixed since then if you go that
route.)


In regards to your issue with compiling, you will need to provide more information. I use both VS 2008 and VS 2010,
both in 32-bit compile on a 32-bit OS and have compiled most revisions since 2142 with no problems. There's any number
of things that could be causing the failure and there's not enough information in your post to say what the problem is...