The loop and data flow is not dead...if going from loop to event driven creates a problem you should ask yourself - Why do I want to change this working code, and is really events the way to go?
Events are still first and foremost useful for GUI stuff in LV so in your case you can always have events react to a "start aquisition" button and so forth, but the events loop is still executed based on data flow so if there are continous processes to be run they should not be within the event case unless you don't need it to catch any other events until the process within is finished...(data flow is still the king). You can have multiple event structures in different loops to overcome this. If e.g. you create a VI that does the aquisition and in that only start the aqui
sition if there is a certain user event, and then in your main VI have a GUI handling event structure that fires the user event for aquisition you'll be free...but still to stop the event a functional global and continous polling is necessary (you can have an event structure with a timeout and poll that for a stop user event instead...but that's not much different.
