I've recently completed an Access application (App A), had the application split into 'be' and 'fe'. Users are satisfied with the application and is now requesting for another application to be developed (App B). The plan is to redevelop disparate databases currently maintained in different systems (some on Linux) into a consolidated and well integrated database.
In order to make it easier for me to manage user requests, I've also developed a simple User Request and Versioning Control application (App C).
The 'fe' will continue to be developed using MS Access. The current 'be' and the new application's 'be' are to be upsized to SQL Server. I'm exploring several approaches and would appreciate any advice rendered:
Question:
1. Should I maintain three separate databases in SQL Server for each applications (App A, B and C)?
2. Should I maintain three separate 'fe'? e.g Have the first fe's Switchboard showing buttons for 'App A' and 'App B'. When the user clicks on 'App A', it brings up 'App A' application. In my initial trial, I notice that it asks for username and password each time the second application is invoked. How can I do away with the second login authentication?
Thanks...
In order to make it easier for me to manage user requests, I've also developed a simple User Request and Versioning Control application (App C).
The 'fe' will continue to be developed using MS Access. The current 'be' and the new application's 'be' are to be upsized to SQL Server. I'm exploring several approaches and would appreciate any advice rendered:
Question:
1. Should I maintain three separate databases in SQL Server for each applications (App A, B and C)?
2. Should I maintain three separate 'fe'? e.g Have the first fe's Switchboard showing buttons for 'App A' and 'App B'. When the user clicks on 'App A', it brings up 'App A' application. In my initial trial, I notice that it asks for username and password each time the second application is invoked. How can I do away with the second login authentication?
Thanks...
