[elricstorm]

Originally Posted by shanejeffery86

Been a long time since I have trolled this thread.

I just got around to creating a new guild and have found need for this mod again.

However, I am having ONE issue with it at the moment.

It is the SAME SQL error that everyone else is getting. I believe that everyone is getting this error because the Armory is acting up BADLY.

Of course, it may be something else that I do not know of. Here is the error I am getting:

First, upgrade to 1.2.0 which fixes some of the bad behavior the timeout settings caused. See if that works. Post back if you have a similar issue. I also see that you are using 3.6.5 and I've only tested this with 3.6.0 and 3.6.7 so I'm not sure what type of behavior it will exhibit on 3.6.5.

Try the upgrade first and I'll try to work with you on your issue and see if we can figure out what's going on. Only a very few people are having issues though. I have similar friends that are using this code on a 3.6.0, 3.6.4, 3.6.5 and I'm using it on a 3.6.7 main and test site.

The armorydata code really does not affect the sql inserts and queries. The armorydata code is just a retrieval mechanism that stores variables that are then used by the queries. The query structure has been in place for all versions. I've only had to slightly modify it.

Just an fyi..

EDIT: Just noticed - you have an "extra" (comma) right after your field11. I can almost bet you a big juicy hamburger that you accidentally placed a comma in vboptions when entering the field ID number. Check vboptions and make sure you didn't place field11, in the option field. That's a "free" field that you can type anything in.