Hi- They recommend for testing and development to use derbyclient so you don't Have that issue. Then for deployment, use the embedded. Is that ok?
Thanks, jim -----Original Message----- From: Marl Atkins [mailto:[EMAIL PROTECTED] Sent: Friday, September 22, 2006 9:33 PM To: 'Derby Discussion' Subject: FW: Dbase Manager Well I figured out a work-around. I just installed the whole Squirrel app into the directory hosting the database. Now if I could figure out how to make simultaneous connections I wouldn't have to keep opening and closing it. Any ideas? Again, this is an embedded database. -----Original Message----- From: Marl Atkins [mailto:[EMAIL PROTECTED] Sent: Friday, September 22, 2006 8:54 PM To: 'Derby Discussion' Subject: RE: Dbase Manager Thanks this looks good but is there any way I can point it at an existing embedded database? -----Original Message----- From: Bryan Pendleton [mailto:[EMAIL PROTECTED] Sent: Thursday, September 21, 2006 6:50 PM To: Derby Discussion Subject: Re: Dbase Manager > I have used Squirrel SQL (http://squirrel-sql.sourceforge.net/) on > another project and found it reasonably ok. I haven't used it with Derby though. Squirrel works great with Derby! Here's a nice set of notes: http://db.apache.org/derby/integrate/SQuirreL_Derby.html thanks, bryan
