dougthomas Moderator
Joined: 27 Jul 2005 Posts: 271 Location: Essex, UK
|
Posted: Aug 22nd, 2005 04:55 AM Post subject: |
|
|
Hi,
Without seeing the code or understanding what the Application is doing and how it's been written, from a purely implementation point of view you have to ensure that potential users have access to the Program .exe and the Database.
If it's not there already you will have to move the Database onto the server you are going to run from, and either put the .exe program file on a shared area where the users can get at it, or install it on each user's machine. If the database Pathname is hard coded in your Application it will have to change to reflect it's new location on the server. The same goes for any other files that may be common to the application that will be server-side.
If the application is there for everyone to use then you won't need to bother about authorisation (ie Logon) if it's not, then you should front end your application with some sort of authorisation mechanism.(Like giving the users a Username and Password and having a Logon screen)
From a more general view, if the Application allows the users to Insert, Delete and Update records, have you implemented a suitable locking strategy ? ie If two users are trying to update the same record at the same time does you code cope ? I don't know anything about SQL Server but I would expect the documentation to have at least one Chapter dedicated to locking strategies.(and the "Deadly Embrace")
Depending upon your original design, you may be in for a bit of re-development to convert from single to multi-user.
Good luck
Regards
Doug |
|