Question re feature/feature request
Posted: Mon Feb 06, 2006 8:50 am
I'm unclear on the logic BE uses when selecting the database that will be opened when the application is launched.
I maintain three databases: my main research database (about 5500 items), and two others (a few dozen or hundred items in each), used to track books that I've ordered for my University's Library or items I've requested via InterLibrary Loan. I could lump all this into one database and use Groups to track this data but: 1) my current approach seems conceptually appropriate; 2) in the event of having to Rebuild a database -- I've had to do this in the past -- I won't lose this most basic division of my data (I do use Groups within each database, for several purposes.)
When I quit BE (if I have to restart my computer for any reason) and relaunch the application, it appears to me that BE automatically opens the last database that was *opened* (?) I think that the more appropriate launch behavior should be the last database that was *edited* or *closed* -- in that way, the user is returned to the last database on which she was working...
An alternative approach might be to define a "default" database in the Preferences, always opened when the application is launched.
TH
I maintain three databases: my main research database (about 5500 items), and two others (a few dozen or hundred items in each), used to track books that I've ordered for my University's Library or items I've requested via InterLibrary Loan. I could lump all this into one database and use Groups to track this data but: 1) my current approach seems conceptually appropriate; 2) in the event of having to Rebuild a database -- I've had to do this in the past -- I won't lose this most basic division of my data (I do use Groups within each database, for several purposes.)
When I quit BE (if I have to restart my computer for any reason) and relaunch the application, it appears to me that BE automatically opens the last database that was *opened* (?) I think that the more appropriate launch behavior should be the last database that was *edited* or *closed* -- in that way, the user is returned to the last database on which she was working...
An alternative approach might be to define a "default" database in the Preferences, always opened when the application is launched.
TH