Hi All, Forgive me for being a bit anal but I always prefer prevention over cure any day.
First I do have a back up of the db. (Access2K)
It is run on a Public drive with controlled folder access and is used by Multiple Users internationally via Citrix software. Assuming Access uses Windows API's to verify the user logged in, no passwords should be necessary.
Upon using the security wizard it will create a new mdw file. Should this be located in the root of the server or would the same folder (a different drive in server) that the db occupies be sufficient?
Currently this is a standard mdb. I tested a FE/BE configuration and for some reason this ran incredibly slow on our network. Not wanting IT to elaborate on lack of funding, I opted to remain with original configuration.
The shift option on open is password protected.
Is there anything that I've overlooked?
Any and all constructive critique will be appreciated.
Thanks.
First I do have a back up of the db. (Access2K)
It is run on a Public drive with controlled folder access and is used by Multiple Users internationally via Citrix software. Assuming Access uses Windows API's to verify the user logged in, no passwords should be necessary.
Upon using the security wizard it will create a new mdw file. Should this be located in the root of the server or would the same folder (a different drive in server) that the db occupies be sufficient?
Currently this is a standard mdb. I tested a FE/BE configuration and for some reason this ran incredibly slow on our network. Not wanting IT to elaborate on lack of funding, I opted to remain with original configuration.
The shift option on open is password protected.
Is there anything that I've overlooked?
Any and all constructive critique will be appreciated.
Thanks.