[dba-VB] SPAM-LOW: Re: Syslogs

Max Wanadoo max.wanadoo at gmail.com
Mon Jun 29 12:44:20 CDT 2009


Well, if you change your mind on the TIMER then you can take this route.  I
have been using it for 8 years now without any problem.

I agree that it can be aggravating when typing code to have it "interrupt"
but that is avoidable if you wanted.

I will see what i can find out re identifying IP addresses.



Max



-----Original Message-----
From: dba-vb-bounces at databaseadvisors.com
[mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: 29 June 2009 18:36
To: Discussion concerning Visual Basic and related programming issues.
Subject: Re: [dba-VB] SPAM-LOW: Re: Syslogs

Max,

I know all this.

I write classes, and those classes can raise events.  Events are much like
this thing of Gustavs, a 
message is sent and if someone gets it fine.  That is often useful

As an example, I cache frequently used data in class instances, one per
record from the table.  It 
would be nice to have a message that is sent to everyone in the database if
anyone modifies the data 
in the cached table.  But I don't want to have to continuously poll a table
looking for a message. 
If a message is sent saying that the cached data changes, then I rebuild the
cache.

That is the kind of thing that this code could possibly add to an
application, HOWEVER... everyone 
has to know the IP address of everyone else that is in the database.

I have been looking for this kind of messaging thing for YEARS.

John W. Colby
www.ColbyConsulting.com


Max Wanadoo wrote:
> Yes, you are correct.
> 
> But your options are (assuming you are going with the access table method)
> is:
> 
> a. you can identity 1 or more individuals via the user table and/or see
who
> is logged in,  or ALL.
> b. you can determine the timer frequency to avoid the problems you
describe.
> c. you can change the timer frequency programmatically if you need to send
a
> FLASH message and then turn it back to "normal speed" after.
> d. you don't need to know any IP addresses or indeed any LAN info at all.
> e. It all happens within Access under your program control.
> f. User can respond, forward, take action etc.
> g. you can check your Outline Emails.
> h. you can call up any Office (or other) app, Word, excel etc (you know
all
> this anyway)
> z. oh, and anything else that Access is capable of...the world (access
> world, that is) is your oyster (or lobster, if you follow Alan's youtube)
> 
> 
> 
> Max
> 
> 
> 
> -----Original Message-----
> From: dba-vb-bounces at databaseadvisors.com
> [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: 29 June 2009 17:58
> To: Discussion concerning Visual Basic and related programming issues.
> Subject: Re: [dba-VB] Syslogs
> 
>  > What I am getting at is, why not just send it to everyone?   Why
> cherry-pick individuals?
> 
> This is an attempt to avoid the timer.  I hate timers, though I use them
in
> a server application. 
> In a user application they cause screen blinking and also cause compile
> errors for the developer if 
> the timer tries to execute code while you are typing in code.
> 
> If I know the IP address of every PC that has an application running, I
can
> send a message to just 
> those PCs.  But I have to know their IP addresses.
> 
> If you are going to communicate through a table then this kind of code is
> unnecessary, but then a 
> timer has to poll for messages in the table.  YUK.
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> 
> Max Wanadoo wrote:
>> Hmmm, ok I will think about that...but when you say "..so that I can..."
> do
>> you mean your application or you as an individual?
>>
>> What I am getting at is, why not just send it to everyone?   Why
> cherry-pick
>> individuals?
>>
>> EG; on one of my apps, I have, oh, all sorts of messages flying around,
> but
>> on each FE there is a timer running on the main menu and periodically it
>> will go to see if there are any messages in the table which handles this
>> sorta stuff.  IF so, the user has a pop up with the option to Sleep for x
>> mins (default to 15) before it reminds again.  It will never go away
until
>> the user has read it, unless you (the originator) says it can time out.
>>
>> Sorta stuff...if you can get my drift.  Don't need to send system
> messages.
>> It is handled with the app.
>>
>> Max
>>
>>
>>
>> -----Original Message-----
>> From: dba-vb-bounces at databaseadvisors.com
>> [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby
>> Sent: 29 June 2009 17:28
>> To: Discussion concerning Visual Basic and related programming issues.
>> Subject: Re: [dba-VB] Syslogs
>>
>> No, I want the Access workstations to log their IP address in a table as
>> Access opens so that I can 
>> read who is available to send messages to.
>>
>> The limitation of this kind of code is that you have to know an IP
> address.
>> John W. Colby
>> www.ColbyConsulting.com
>>
>>
>> Max Wanadoo wrote:
>>> Do you mean IP address without having to go to the other workstation.
>>>
>>> If you just want to know what the IP address is, use VNC or RealVNC then
>> you
>>> can just hover the mouse over the system tray icon and it will tell you
>> the
>>> ip address.
>>>
>>> Max
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: dba-vb-bounces at databaseadvisors.com
>>> [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby
>>> Sent: 29 June 2009 16:53
>>> To: Discussion concerning Visual Basic and related programming issues.
>>> Subject: [dba-VB] Syslogs
>>>
>>> Hmm...
>>>
>>> Looks quite cool.
>>>
>>> My mind is a raging torrent, flooded with rivulets of thought cascading
>> into
>>> a waterfall of creative 
>>> alternatives.
>>>
>>> Now... how do we determine the IP address of every machine using an
> Access
>>> application on the local LAN?
>>>
>>> John W. Colby
>>> www.ColbyConsulting.com
>>>
>>>
>>> Susan Harkins wrote:
>>>> <http://www.devx.com:80/vb/Article/42242/0/page/1>
>>>>
>>>> I'm so proud... ;) <sniff> Notice, my name is NOT in the byline... I'm
> so
>>>> proud... yet another ones passes safely to single author status. :)
>>>>
>>>> Susan H. 
>>>>
>>>> _______________________________________________
>>>> dba-VB mailing list
>>>> dba-VB at databaseadvisors.com
>>>> http://databaseadvisors.com/mailman/listinfo/dba-vb
>>>> http://www.databaseadvisors.com
>>>>
>>>>
>>> _______________________________________________
>>> dba-VB mailing list
>>> dba-VB at databaseadvisors.com
>>> http://databaseadvisors.com/mailman/listinfo/dba-vb
>>> http://www.databaseadvisors.com
>>>
>>> _______________________________________________
>>> dba-VB mailing list
>>> dba-VB at databaseadvisors.com
>>> http://databaseadvisors.com/mailman/listinfo/dba-vb
>>> http://www.databaseadvisors.com
>>>
>>>
>> _______________________________________________
>> dba-VB mailing list
>> dba-VB at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/dba-vb
>> http://www.databaseadvisors.com
>>
>> _______________________________________________
>> dba-VB mailing list
>> dba-VB at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/dba-vb
>> http://www.databaseadvisors.com
>>
>>
> _______________________________________________
> dba-VB mailing list
> dba-VB at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-vb
> http://www.databaseadvisors.com
> 
> _______________________________________________
> dba-VB mailing list
> dba-VB at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-vb
> http://www.databaseadvisors.com
> 
> 
_______________________________________________
dba-VB mailing list
dba-VB at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-vb
http://www.databaseadvisors.com




More information about the dba-VB mailing list