I'm using HeidiSQL from the developer of Front-SQL. When I make any changes to my database, it shows me the SQL statement equivalent of the change I just made. So, I make all the changes I'm going to, copy all the SQL I used and then I trim it down to the smallest necessary number of statements. Using this program, I can also see the table layout, the data, and construct my own SQL statements to query the database all in the program.
If you haven't checked it out already, I'd give it a shot. It's a nifty little program with a lot of features and it's free. The only problem I see with it is that it associates itself with the .SQL extension. I haven't figured out exactly what opening an SQL file with the program does, yet, but I'm also not wanting to find out given that the EQ database is the only one I have. =P
I think I'll probably download the program you've directed me to this weekend and give it a go, but, in my opinion, the program I'm using is already damned convenient. =P When I was using Front-SQL, I was always having to query the database from the MySQL prompt rather then in the Front-SQL program, but the Query ability seems to work in HeidiSQL and gives me a quick way to go back and forth between Queries and data. =)
As I pointed out to someone requesting a #DoorInfo command--- Najena door fixes took me a whole 20 minutes to fix and then release to here and most of that was clicking a door several times and alt-tabbing out to see the information dump in the zone window so I could figure out what door. As far as the SQL went, HeidiSQL made that part easy. =D
|
Threaded Mode
