We use Access 2010 to run a database containing customer orders created by our sales staff. Some of the customer information is also used in a second database for a different purpose.
I would like to provide a command button, or similar, on the customer order form which would launch the second database and open the appropriate form, pre-populated with the customer details from the first form.
I appreciate that the easiest solution would be to merge the two databases, but there are a number of reasons why they are best kept separate.
I've managed the first step. A command button runs an append query which imports the relevant information to the second database. Is it possible or advisable to extend the VB code behind the command button to launch the second application and open the form?
Any advice would be much appreciated.