Zugg Software :: View topic

Posted: Fri Aug 15, 2003 1:05 pm

Hi,

I created a db which from time to time i would like to query as i mud through the command line. I am also working on another database through the gui interface as and when i have something to update it with. Ive read how the #dboffline command enables a script or a command like query to work in the background on a database while you can work on a different view on a different database via the gui.
I seem to be having problems with this as it seems to lock the gui e.g i cant close a database or load a database. I have to actually close the database window and turn it back on. I also get violation errors when i try to edit a record.

what i am doing

* i open up my database that i am still working on via gui
* through an alias i run via the command line it does a #dbload
on a database queries it outputs info i want and then does a #dbclose.
I make sure the #dboffline is set so it doesnt interfere with the gui.
Ive tried it with having both dbs loaded in memory and not closing the queried one

any suggestions?

on another note if a field in a db cant be edited. i.e doesnt update with new entry does this mean that it has possibly become corrupt?

thanks

mortie Smile

ps i'm using 6.62

GURU Joined: 26 Jul 2001 Posts: 1958 Location: Canada

Haven't ever tried to work on two databases simultaneously. I've always had one open/active at a given time. Maybe another has tried this.

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

#DBONLINE and #DBOFFLINE affect all open databases. Or, to be more precise, they affect the user-interface regardless of what database it's showing.

Posted: Sun Aug 17, 2003 3:39 am

the online help file says :-

"zMUD also has a powerful way to perform scripts in the background without effecting the user interface. The user can be editing a different view of a different database while your script is running.

To work in the background, use the #DBOFFLINE command. Now, all database commands and functions will work as normal, but no changes will be displayed in the database user interface. "

I just assumed this meant that you could do a quick query for instance of a database that isnt currently loaded, load it up in offline mode then close it again. with all this not messing with the gui and the current db being worked on

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

The offline help file says the same thing.

You don't have to close the current database to open another one, whether you have #DBONLINE or #DBOFFLINE. However, if you open a second database using #DBLOAD, while in ONLINE mode, it will replace the previous database as the one SHOWING in the database window. Both databases will still be open.

I'd recommend against using #DBCLOSE. That's where the errors seem to crop up. Just leave both databases open, with the one you want to see selected in the database window.

Posted: Wed Aug 20, 2003 5:17 am

things are working ok now

I stopped using #dboffline/#dbload via the command line. Loaded both dbs from the gui and i can perform queries on one of the databases from the command line and am still about to work on my other database.

thanks for the help

mortie [:p]