Hi Ravi,
Is it okay if I am following this approach ?. I feel my approach is fine because when the application starts up the client must totally be transparent to which database he is getting connected to.
No because of the following requirement in the instructions:
Note: your program must run correctly no matter what directory it is installed in.
If answer to the above question is 'No' then should I save the db.db file in some location say <INSTALL>/database/db.db and then specify the path to db.db file as a parameter in the command line instruction so that I am not hard coding it in my code ?
That's what you need to do. You can just put db.db in the same directory as your executable jar and document that fact. You don't have to allow selection on the command line if you don't want to but many, including myself, have done that.
Hope this helps,
Michael Morris
[ September 21, 2002: Message edited by: Michael Morris ]
Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius - and a lot of courage - to move in the opposite direction. - Ernst F. Schumacher