Are you trying to view the entire database at once? Or just one table at a time? If you're only looking at one table, then having a timer to just refresh your data may be enough depending on your needs and how large the table actually is.
If you don't mind adjusting your table, then add a last modified field to it (and a last modified by field is usually also good) and then use a SQL (or whatever database structure you're using) query/stored procedure to check for any rows that have updated since your last check. This tends to be low overhead on the server even with checking regularly. Then, you can just load in only those changed rows instead of the entire table.
It's just a text file with a list of clients and related information, separated by tabs. I can quite easily modify it if required. I thought about adding a unique id to each entry and somehow sending a signal to the other clients with a list of the ids that have changed rather than reloading the whole thing.
There's literally about 80 items at the moment and it shouldn't get much bigger, as items are deleted too.
But in your first post you said everyone would work with the same mIRC instance.
Do you mean they all launch it from the same network share?
Yes, they launch it from the same mapped network drive. Three people on three different computers, log onto three different terminal server sessions, and launch the same installation of mirc from a mapped network drive. Any of those people can update the file at any time, but the changes won't be updated in the @window for the other people who are also logged on.
The other option I have, but that I don't want to go down, is that I could make it so only one person can access the database at once. I'd prefer not to do this if it can be helped.
------
Brainwave!!
I could write all of the amendments to a changes.txt file, and make sure that the script reads and updates all of those modifications in the db before making any changes of its own. It doesn't necessarily need to be updated in real time.
Does that sound good? Can anyone foresee any problems with that?
