Frank,
I apologize for the delayed response.
The problem is that MyEclipse does close the connection to the database, but because of the special nature of the embedded Derby driver, the database itself will not shut down, disallowing access from other JVMs.
The database will only shut down if
a) The JVM which started it explicitly shuts down the database
or
b) The JVM which started it terminates
MyEclipse currently does not do (a) as we do not currently recognize the Driver as a special case which needs additional post close processing. I have filed a bug report about this particular issue.
In the meanwhile, I have the following suggestion:
1) Start a Derby network server from your command line, you can point this to the same database being used by the embedded driver. (Make sure your RCP app is not running at this time)
2) Create a MyEclipse driver using the network client driver (and not the embedded driver) and connect to the network server you started above.
3) When done, close the connection and stop the network server
4) Start RCP app
Note that neither the RCP app nor MyEclipse will be able to access the DB simultaneously, but my asking MyEclipse to connect using the network client driver instead (and starting and stopping the network server), you can start your RCP app without having to shut down MyEclipse each time.
I hope this helps, please let me know if you require further assistance.