I have an Access 2002 app using TS on Windows 2000 Server with a max of 8
concurrent users.
Each user has its own space on the server with its own copy of the front
end. The start up command line points to this front end and they all share a
common MSAccess.exe on the server.
I am looking to deploy an Access 2002 app using TS on a client's Windows
2000 Server. The client does not have Access installed, so I've created the
install using Wise Standard and the SageKey object (using the 'Standalone'
template).
I intend creating a separate folder on the server for each user, and
installing the full runtime into that folder.
Is this the best way to to it, or should I be looking at placing the runtime
files (msaccess.exe, Jet etc) into a shared folder, so that each user only
has a copy of the front end?
Is there a problem installing and running multiple copies of these runtime
files on the same computer?
Would there be a significant performance difference using shared files?
Space on the server is not an issue.
--
Bob Darlington
Brisbane
concurrent users.
Each user has its own space on the server with its own copy of the front
end. The start up command line points to this front end and they all share a
common MSAccess.exe on the server.
I am looking to deploy an Access 2002 app using TS on a client's Windows
2000 Server. The client does not have Access installed, so I've created the
install using Wise Standard and the SageKey object (using the 'Standalone'
template).
I intend creating a separate folder on the server for each user, and
installing the full runtime into that folder.
Is this the best way to to it, or should I be looking at placing the runtime
files (msaccess.exe, Jet etc) into a shared folder, so that each user only
has a copy of the front end?
Is there a problem installing and running multiple copies of these runtime
files on the same computer?
Would there be a significant performance difference using shared files?
Space on the server is not an issue.
--
Bob Darlington
Brisbane
Comment