Moving Database To Asatahost it wont work and I need help

Ok, since my application has been accepted, I now like to move my site from http://forums.xisto.com/no_longer_exists/ to http://forums.xisto.com/no_longer_exists/.

My site runs geeklog so I do need the database.

I've tried everything, make a back-up using geeklog and uploading it using cpanel, exporting it using phpMyAdmin 2.5.3-rc1 (on superihost, which works terribly slow) with all kind of setting and uploading it using cpanel, but the only thing it creates is an empty database

What am I doing wrong ??? (xcept selecting wutske_geeklog)

This is the export page, what do I have to change ???

Well from the looks of your screenshot it will work except you just need to check Save as file" then you should get a popup window and you would save this file wherever you want. After you have the new sql 'dump' you would go to C Panel in Xisto and create a new database and enter that data base and just click the sql link and tell it to browse your local hard drive for the file you have just downloaded and it will then 'dump' that data into the database you are currently in and you should be ready to go.If you get errors something is wrong but this is not very common since phpMyAdmin made the file in the first place, it is merely reading back a file it made in the first place.

Not sure if you tried this, but log in to your Xisto cPanel now. Go down to the Site Management Tools section and click on Backup. Look for your database (wutske_geeklog) under the Download a SQL DB Backup (Note: Do not try to open this file in winzip.) heading. Click on it and it should popup a window. Save it somewhere.

Now go to your new account and login to cPanel. Go to the Backup section again. Under Restore an SQL DB (at the bottom), click on the Browse button. Look for the SQL backup file you downloaded earlier and upload it back to the new webhost account.

That should make it work. If not, for the new account is it using the same prefix (wutske_) as your old database? I'm no expert with SQL, but I think if the prefix is different, it will cause problems. So make sure that when you set up the new geeklog install on that webhost (Xisto), that you set it up so that the SQL database name is wutske_geeklog.

Once you have the file on your computer that you downloaded from your old host, go into cpanel on you Xisto account, go to mySQL databases. Create a new database. Click on phpmyadmin further down the page. From the dropdown box on the left hand side, select the new database. Select SQL from the pane that just loaded. There should be a Browse button there. Click on it and select the file that you downloaded from your old host. Click Upload and you should be done. If you need anymore help, and trust me with your password, PM or email me, send me the file and your cpanel password and I'll do it for you.

As houdini said, make sure you check...Save As File.Then put compression to gzip. (not needed, but better off as).Then download set file.Once you have the file log into your Xisto account.From there create a database with the same name as the one from superiorhost.com, or you'll have to change things manualy.After that, important the saved file to that database.Now, you aren't done yet.You still need to copy every file from your geeklog directory at superiorhost.com, and then put that directory onto your Xisto website directory.If you follow those steps accordingly, there shouldn't be a problem...Minus changing some links around .BUT, whatever you do:DO NOT edit anything inside your database, gzipped, file. Nor inside your database.DO NOT do a fresh install of geeklog.You won't be needing to install anything like you did for superiorhost, as this is strickly a import/copypaste situation basicly.Follow what I said accordingly, and it should work fine.

Nope, nothing works, the database remains empty .Doesn't realy matter anymore, I've manualy moved everything. Only thing I can't move are the comments, but the homepage only contained 3 comments.

In case your interested knowing what was the issue, you could take the back up and post the text it generated (ie. SQL code) here so we can analyze it.