A client would like to be able to launch an Access program from a Foxpro program. Is there a way to launch the Access program as a separate task so that it doesn't suffer any performance hit from Foxpro overhead? Is RUN /N the way to go or is there an API call or something else that is better?