T
TheScullster
We have a split database (developed with Access 2000) and are looking to
replace the server on which the back end is stored.
Currently the back end is on NT4 server box, but this is likely to change to
a Windows2003 Server box.
The front ends live on Win98 and NT4 machines (hopefully soon on XP PCs
also).
Will the back end be OK on 2003 Server?
The front ends currently connect to the back end referencing a mapped drive
letter g:\. This is defined in user login scripts. If we map a location on
the new server to this same letter (changing the login scripts accordingly),
will the database function correctly without re-linking the front/backend
tables?
Are there any other issues that I should be aware of?
TIA
Phil
replace the server on which the back end is stored.
Currently the back end is on NT4 server box, but this is likely to change to
a Windows2003 Server box.
The front ends live on Win98 and NT4 machines (hopefully soon on XP PCs
also).
Will the back end be OK on 2003 Server?
The front ends currently connect to the back end referencing a mapped drive
letter g:\. This is defined in user login scripts. If we map a location on
the new server to this same letter (changing the login scripts accordingly),
will the database function correctly without re-linking the front/backend
tables?
Are there any other issues that I should be aware of?
TIA
Phil