problem w/ SQL server and NewClass Weapon

Ive used TXT version 8920 SVN and all are fine running with no or minimal errors, new classes can equipt there weapons like gunslinger soul linker etc.. etc..., but i wanted a CP so i decided to change txt w/ SQL version 8920 SVN. I completely deleted my TXT server and install the SQL version. now when a new class is created they cant equipt weapons....

ive search the server files and cant seem to find what ive been missing, please help if you now anything about equipting weapons and item w/ there respective classes.

ps. if GM account of course it can equipt anything, but normal players cant. tnx in advance.

Hmm. I guess it about table problem i guess? Did you execute the .sql files? you need to execute them =)

yes ive executed all the files inside the eAthena\sql-files ...

Hey. Do you excute some more code? I remember that you need to excute 3 sql-files and some code. For the code i already forget...

oh.. all i did was execute all the files inside sql-files folder like the guide says it doesn't mention anything about the code. anyone remember what code will i need to execute?

these are the files inside my sql-files folder:
convert_engine.sql
convert_password.sql
db_tables.sql
item_db.sql
logs.sql
mail.sql
main.sql
mob_db2.sql
mob_db.sql
oA2eA-rc5.sql

and a bunch of update_xxx....sql


anything im missing??? tnx and really appreciate it..

Ya. I think you didnt excute the code. That code is just 2 line longs..... Maybe it looks like this

Code:

---

INSERT INTO login VALUES
('s1,'p1','0','0','0','0')

---

I already forgot the code. I can get it if Eathena is open.

I think i have executed that one, its where the part you change the S1,P1 with ragnarok, ragnarok in most guide right?

Hm... Its not exactly the code but the actual SQL string itself... It seems like you've got a bad DB in SQL with bad items.. You're going to have to get some good working SQL files and switch them with your other tables. Otherwise it looks like you're going to have the same problems as before. I hope this helps.

Problem solved, i drop the itemdb table and reload it with the one from 8993.