send command to other users within access

Hello,

I'd like to send command or message within access to other users who are
connected to the same mdb file.

Is that possible ?

thanks in advance.

Nader

"Nader" <nader@infomaniak.ch> wrote in message
news:4491395c$0$719$5402220f@news.sunrise.ch...[color=blue]
> Hello,
>
> I'd like to send command or message within access to other users who are
> connected to the same mdb file.
>
> Is that possible ?
>
> thanks in advance.
>
> Nader
>[/color]
Yes, use a form in conjunction with the form's timer event. Use it to check
a flag in a table. If the flag is set, open a dialog form with your custom
message which could, for example, be stored in the same table as the flag.

HTH - Keith.
www.keithwilby.com

isn't that timer going take more of my cpu perfomance or at least more
memory usage ?

"Keith Wilby" <here@there.com> a écrit dans le message de news:
44913b53$1_1@glkas0286.greenlnk.net...[color=blue]
> "Nader" <nader@infomaniak.ch> wrote in message
> news:4491395c$0$719$5402220f@news.sunrise.ch...[color=green]
>> Hello,
>>
>> I'd like to send command or message within access to other users who are
>> connected to the same mdb file.
>>
>> Is that possible ?
>>
>> thanks in advance.
>>
>> Nader
>>[/color]
> Yes, use a form in conjunction with the form's timer event. Use it to
> check a flag in a table. If the flag is set, open a dialog form with your
> custom message which could, for example, be stored in the same table as
> the flag.
>
> HTH - Keith.
> www.keithwilby.com
>[/color]

but what do u mean by check a flag in a table ? is this an option when u
create a table ?
"Keith Wilby" <here@there.com> a écrit dans le message de news:
44913b53$1_1@glkas0286.greenlnk.net...[color=blue]
> "Nader" <nader@infomaniak.ch> wrote in message
> news:4491395c$0$719$5402220f@news.sunrise.ch...[color=green]
>> Hello,
>>
>> I'd like to send command or message within access to other users who are
>> connected to the same mdb file.
>>
>> Is that possible ?
>>
>> thanks in advance.
>>
>> Nader
>>[/color]
> Yes, use a form in conjunction with the form's timer event. Use it to
> check a flag in a table. If the flag is set, open a dialog form with your
> custom message which could, for example, be stored in the same table as
> the flag.
>
> HTH - Keith.
> www.keithwilby.com
>[/color]

"Nader" <nader@infomaniak.ch> wrote in message
news:4491510c$0$723$5402220f@news.sunrise.ch...[color=blue]
> but what do u mean by check a flag in a table ? is this an option when u
> create a table ?[/color]

Using the timer event will be no noticable overhead on your PC if you set an
interval of, say, 15 seconds. I'm suggesting a table with two fields,
"Flag" (Yes/No) and "Message" (text). Your main form's timer event would
poll the "Flag" field every 15 seconds and do nothing if it returns false.
If it returns true then a second (dialog) form would open and display the
message in the "Message" field.

HTH - Keith.
www.keithwilby.com

If you want it to be unique to user, you would have to add userid or
logon id to the table.

Also will have to have some type of delete logic involved, in all
cases. so that after the user has read it then the message is deleted.
(or add a read flag and have the reading process set that flag)
Otherwise the same message will keep coming up over and over.

If it is for all users (not just one) you will have to think about
knowing who has seen it and who has not and how to keep it from coming
up over and over and over and over.
[color=blue]
> www.keithwilby.com[/color]

"Ron2006" <ronnemec@hotmail.com> wrote in message
news:1150380913.644098.166690@h76g2000cwa.googlegr oups.com...[color=blue]
> If you want it to be unique to user, you would have to add userid or
> logon id to the table.
>
> Also will have to have some type of delete logic involved, in all
> cases. so that after the user has read it then the message is deleted.
> (or add a read flag and have the reading process set that flag)
> Otherwise the same message will keep coming up over and over.
>
> If it is for all users (not just one) you will have to think about
> knowing who has seen it and who has not and how to keep it from coming
> up over and over and over and over.
>[/color]

All valid points and it makes me wonder why the OP would want to do this.
Is it so as to be able to ask users to log out when BE maintenance is
required? If so then there are more elegant ways to achieve this than to
send them a message and rely on them actually being there and complying with
your request.

Regards,
Keith.

My 2 cents.
I have been doing this for several years in our database. We
use it kind of like an instant messaging system. "Hey did you get me
that Part Number" Yes, its 1234" I set it up like an email system.

As the other posters suggested, its just a table. I have the
Senders ID the Receipient(s) IDs, the subject, the message, the Time
sent, and whether is was read or not. Each user sets up a time to be
reminded of messages from One Minute to One Hour and on his front end
only, I look for messages at that periodic rate. As suggested before,
there seems to be little overhead penalty.

It's a convenient, if unsophisticated tool. One good thing is
we have a permanent record of the entire diatribe.

It you need more help, let me know.

Hank Reed

Thanks to all of you.

I'll try this solutions right away.

"Hank" <hankrunner@aol.com> a écrit dans le message de news:
1150389535.964749.111960@g10g2000cwb.googlegroups. com...[color=blue]
> My 2 cents.
> I have been doing this for several years in our database. We
> use it kind of like an instant messaging system. "Hey did you get me
> that Part Number" Yes, its 1234" I set it up like an email system.
>
> As the other posters suggested, its just a table. I have the
> Senders ID the Receipient(s) IDs, the subject, the message, the Time
> sent, and whether is was read or not. Each user sets up a time to be
> reminded of messages from One Minute to One Hour and on his front end
> only, I look for messages at that periodic rate. As suggested before,
> there seems to be little overhead penalty.
>
> It's a convenient, if unsophisticated tool. One good thing is
> we have a permanent record of the entire diatribe.
>
> It you need more help, let me know.
>
> Hank Reed
>[/color]

I'd love to know about the other ways you have in mind. I use a table
similar to the one described and would love to know another way to go at it.

<w_a_n_n_a_l_l_ -@-_s_b_c_g_l_o_b_a_l._n_e_t> wrote in message
news:B1okg.44942$fb2.33497@newssvr27.news.prodigy. net...[color=blue]
> I'd love to know about the other ways you have in mind. I use a table
> similar to the one described and would love to know another way to go at
> it.[/color]

Why bother asking the user to log out when you can force them off without
their intervention? You'd still use a table but that table would contain
either a time to log off, a specific user to log off or a specific computer
name to log off. It's a system I use and it works without fail.

Keith.