Zugg Software :: View topic

Beginner Joined: 10 Jul 2005 Posts: 28

Well, I was messing with my little database script that you all helped me with, it worked before, the only thing I added was a #PR Item.ID "Enter the item id please" to get the id. It came up, I tested it... didn't go into the database, as in none of the variables did, which they'd done prior. So I open up the variable Item, and sure enough, all the data is there, even the ID, but it didn't save to the database for some reason. So I mess around a bit, I honestly can't remember what I did, and then all of a sudden the next time I try to open the database viewer I get

Access violation at 0084464B of module Zmud.exe, and then I can't remember the second part (forgot to write the whole thing, it was 000000CC or something like that.) And then zmud freezes. I restart zmud, same thing. So I rename my mud settings, connect offline, it creates a fresh mud settings, I import all my crap, and then reconnect. This time, I don't get an access violation, but rather the database viewer doesn't open now! At all! When I click on it, I see the main zmud window gray (lose focus) but nothing comes up. Any clues? I'm running 7.13b on WinXP. Plent of ram/proccessor/hd space. It's installed on the admin account

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

You could try to reset the windows. If you see ZMud send focus away from the game window but nothing happens, this is usually the culprit. Anything else is likely to be some sort of application corruption and you'd have to reinstall and stuff.

Resetting the windows is, I believe, found on the Layout menu.

Beginner Joined: 10 Jul 2005 Posts: 28

Ok, that took care of that problem! Thanks. Now I just have to figure out why it will pick up all the variables still, and the trigger to save all the variables to the db fires, but the information doesn't get saved...

Anyone happen to see anything wrong with this trigger?

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Try surrounding everything but #T- blankline in a #PRIORITY {}. My guess is that the trigger is processing so fast that the database stuff doesn't get a chance to process. I've had this problem before with other non-database issues.

And, just to get this stupid question out of the way, you know that in order to use the database the Database Module window has to be open (doesn't need to be docked or visible above any other windows), right? If it's not open, the trigger will still fire but none of the database stuff will do anything.