Hi again
There are probably better ways of doing what you need then my suggestion,
but that said, I think it would be extremely simple to implement, but maybe
it wouldn't give you the functionality you need, but anyway, just to
continue down the thought process....
perhaps if you defined a list of events that you are interersted in, when
any of the events are triggered (in either app) you could write details to a
table which is accessible by both apps i.e.
in Access, if you load form "main", then you write to the table some thing
like "ACCESS,FORM_OPENED, main", when you close the form write
"ACCESS,FORM_CLOSED, main", you could be doing exactly the same in your .net
app this time something like "NET,FORM_OPENED, form7", when you close it
write "NET,FORM_CLOSED, form7", etc... i.e. this table would contiain a
running list of events, and the last entries of any particular category
would be the 'live' status available to be queried at any time. Maybe you
could even extend it to write a full structure to the data table.
Finding the status of App 1 on demand would be simple i.e. run a simple
query, that reads the result into a structure which you could use in the
rest of the App 2 program and vice-verse.
In each app, in the background maybe you could have some code that regulary
checked the status of your common table, that way if App 1 has a change then
within a very small time, app2 would know about it i.e something similar to
an event driven interrupt.
as I say, its probably no good to you anyway but always worth thinking of
different ways to solve a problem 8-)
hope its of some help
Andy
p.s. I'm not an expert, and I'm not sure if VB supports interupts, but in
the olden days I seem to remember you could set your software to check for
predifined events monitored in the background by the operating system, the
code would run without you worring you too much, but if the event occured
i.e. something changed, the OS would notify you, and you could set your
software to go off and do the necessary and when it was done, return back to
the place where the event occured (or that was the theory anyway )
"Gerald Bader" <ge****@gmx.at> wrote in message
news:OY**************@TK2MSFTNGP14.phx.gbl...
Hi!
Thanks for your reply.
"aaj" <aa*@aaj.com> schrieb im Newsbeitrag
news:41***********************@news.easynet.co.uk. ..
I know it probably isn't as technical as it might be, but could you not
use the access database as a common entity between the two.
Maybe you could use events from both the .net and the access, and write
the current information from each to a common table.
Each app could then be triggered (timer/interrupt?) to see the current
status of the other from the common table
What I meant with "real-time" is that one application should "ask":
"What's
your current form?" and the other one should immediately "answer": "Its
name
is 'Main-Form'."
If I use a timer, the user always had to wait until the Timer-Event was
fired.
I rather thought of the capability of the two applications to run
functions
each within the other application.
But the problem is how to "find" the "application" object (or how you want
to call it) of each the other application within the current Windows
session.
Besides - what is an 'interrupt'?
Or is there possibility to send any Message from one application to
another,
never minding if it is a .NET or a COM application?
hope it helps
Andy
Gerald
