Can vb 2005 exe run even in VB 6 exe

I've looked at the question. The point is that you don't want a timer event. A timer event, plainly enough, goes off when a period of time elapses. That's the point.

You want another event.

I am on holiday currently, and nowhwere near a development machine, but I'm pretty sure that ADO supports Update events, i.e. an event triggers when a recordset gets updated - which seems to be what you are looking for)

Connections have an ExecuteComplete Event:

An ExecuteComplete event may occur due to the Connection.Execute, Command.Execute, Recordset.Open, Recordset.Requery, or Recordset.NextRecordset methods.

Click to expand...

Recordsets have a FetchComplete Event, RecordChangeComplete Event, etc.

Hey strongm. Thanks for responding. Enjoy your holiday!

I looked at the other thread and now it seems as if something else is actually desired.

You need to use some form of IPC to send an alert from the updater to the displayers. A mailslot broadcast or UDP broadcast seem obvious choices now that NetDDE isn't supported anymore. MSMQ might also be an option but could be overkill here. There are also ways to use an ActiveX EXE to relay events to multiple subscribers via DCOM (the good old Coffee Monitor example from the VB6 manual comes to mind here).

Thanks for the reply dilettante. I had thought about ActiveX EXE approach. I remembered reading about them in one of Strongm's examples about property bag. Not sure if this is the approach to take or not.
I appreciate your input.

> now it seems as if something else is actually desired

How so? The OP states "The 2005 application feeds the database with data that the VB6 application displays", which would pretty much seem to me to make it a prime candidate for responding to one of the RecordSet events

As far as I know these events are notifications regarding actions that you (your process) initiates. They're basically detailed progress events.

I don't see anything like a "Hey, new data" or "Somebody else updated something" event. Actions by an external process have no communication path back to you through ADO events.

I've never read anything to the contrary, but if somebody has an example or can give a reference I'd find it useful.

ADO Event Handler Summary

Sorry, yes, see what you mean. Mind clearly turns to putty after two weeks of vacation ...