Sending a message to all users

[branston]

Hi,

I have a database with muiltiple users being able to enter the front end at the same time. Is there a way that if a button is pressed in ANY copy then a pop up appears on ALL the users screens? Basically i want a way of saying from my copy that all the users must exit the database so i can make updates etc.

Any ideas?

Thank you!

 

[DCrake]

You should not have multiple users all opening the same front end. Each user should have their own copy on their own workstation. This will enevitable lead to corruption, not only in the front end, but more crutially, the data.

This also means you can wok on development then deploy an updated version to all users. This is the ball ache part of the procedure but the best in terms of secrurity and peace of mind.

It only takes one user to do something untoward and all the system is down. How long have you been operating like this?

David

 

[branston]

Thanks. I will try and think of a way of distributing the front end. This may well solve some other problems ive been having.

However... this still doesnt give me a way of getting a message to everyone who is using it if i need to get them out of the whole thing (i.e. so i can make changes to that back end)

 

[NigelShaw]

Hi

a very crude way could be to add a timer event to check for a value in the back end say every 5 minutes. If the value is there, show the message.

Then from your side, enter a message for the front end to display and make a simple on off switch to change the value when you want the message to be displayed. This way you could add your own message every time. You could also go one step further and this could filter a message down to single users if required by the front checking for a true value to show the message, a text value to show the message and an id or name to show the message only to that person.

Then, if you managed to get this far, you could probably create an internal message board between all of your users but I'd concentrate on part 1 first...

( see how things can so easily escalate

regards

Nidge

 

[Mr. B]

branston,

If you get the front-end file distributed to all of your users where each one has their own copy on their on workstation as as been suggested, you would most likely not even need to send them the type of message that you are describing.

When each user has their own copy of the front-end, you can make all the changes you want or need to make in the front-end and then when you are ready you can just deploy the new front-end and each user would get the new copy of the front-end.

Do a search for "Replacing the Front-end" or "Auto FE Updater"and you will find that there is a great utility already available for doing this.

Here is a link that should get you there:
http://autofeupdater.com/

 

[boblarson]

Do a search for "Replacing the Front-end" or "Auto FE Updater"and you will find that there is a great utility already available for doing this.

Here is a link that should get you there:
http://autofeupdater.com/

And another type of one is on my website (mine is different from Tony's as his uses a separate database and ini files, whereas mine enables each individual frontend to do autoupdating and doesn't rely on any external tools. See my signature for the location of mine.

 

[branston]

Thanks for all your suggestions. I am aware that i would be able to change and update the front end very easily in this case, but i need the message ability to get people out of the back end as well.
NigelShaw - thanks for your suggestion, i will have a think of how i can apply that idea.

 

[DCrake]

One solution is to have a hidden form that has a timer on it, say every minute. What it needs to do is to check for the existance of a certain text file in the same location as the data mdb. Inside this text file is a message that will be displayed in a message box.

From your machine create a text file called Warning.Txt then copy this to the above location.

When the timer hits zero

If Dir(<<PathAndFileName>>) <> "" Then
   Me.TimerInterval = 0
   Dim Msg as String
   Open <<PathAndFileName>> For Input as #1
   Msg = Line Input, #1
   Close #1
   MsgBox Msg, vbExclamation+vbOkOnly,"Message From Administrator"
End If

What will happen is that as soon as the timer finds the file it will display a message box telling them to log out.

To make this more useable on the OnLoad event of the application get it to do the same. So if they try to log in too soon it will detect the file and inform the user


StartUp Form OnLoadEvent

If Dir(<<PathAndFileName>>) <> "" Then
   MsgBox "The application is currently unavailable, please try later.",vbInformation+vbOkOnly,"Message From Administrator"
   DoCmd.Quit
End If

So when you have done you work you simply delete the text file from the server location and everyone will be allowed to log in again.

This code is aircode and as such is untested.

David

 

[NigelShaw]

Hi

DC, what if the txt file is found and then deleted? Bizarrely enough, I found an employee of mine lately with 2 windows open and he was opening a db to check for folder changes so people do do it for whatever reason they may have....

I have nearly finished a sample db that has an admin page ( which could be moved to a simple admin db ). This allows a Boolean option and message input. Another form ( which can be moved to a front end ) runs a timer that runs a check every 5 mins or so looking for the value. When the value is set through the admin page, the timer picks it up and displays the message. Then gives the user a few minutes ( same time used to check for the Boolean ) to close before it closes itself.

You can do with it what you want and I'll try and post it up tonight.


Regs

Nigel

 

[NigelShaw]

Hi Branston,

the attached might work for you. its a simple admin process ive knocked up to control the users forms.

you'll get the gist.



HTH


Nigel

 

[DCrake]

Nigel,

The file can be hidden in the folder so as long as the setting is turned on they woin't be able to see it. And if you have staff that are rummaging around your server I would change their profile as they are a potential danger.

David

 

[NigelShaw]

Hi David,

that particular staff member was removed completely........

regs

Nigel

 

[MarkK]

And you could implement this inside your system by writing to and reading from a table.

 

[NigelShaw]

Hey look, a fellow Cad person

who is the question directed at?

Nidge

 

[branston]

Nigel, This sounds like it would be great - but i cant seem to open it... is it in an access version later than 2003?

 

[NigelShaw]

Hi Branston,

its 2007, sorry. always best to put what systems you use in your sig. i'll convert it and re-post in about an hour



regs

Nidge

 

[branston]

Oh thank you so much, thats very kind. Looking forward to having a look!

 

[NigelShaw]

Hi

here is the 2003 version/

regs

Nigel

 

[NigelShaw]

Hey

did it work for you? Was it what you needed? It's good practice to respond and let people know if it does / doesn't work.

Cheers

Nigel

 

[branston]

Nigel,
So sorry for not replying, I have been a bit manic recently. In the process of getting this into my db but at the moment it looks like its working a treat.

Thank you!