B
BWS
Access 2003 problem
I have a daily automated job that creates multiple .csv files on a UNIX box,
and then FTP's these files to a read-only directory on an NT box, stomping on
top of the previous day's files.
There are many users opening and linking to these files via Excel and MS
Access.
I was surprised to learn that MS Access will still lock these .csv files
even though the user only has read-only permission.
This effectively does two bad things. If a user keeps Access open through
the night, my job fails because the files are locked. Also, there seems to
be more and more contention problems between users of this data, when one of
them is using MS Access.
Is there any way to force MS Access to play nice with Excel concerning
multiple users of a read-only .csv file?
I have a daily automated job that creates multiple .csv files on a UNIX box,
and then FTP's these files to a read-only directory on an NT box, stomping on
top of the previous day's files.
There are many users opening and linking to these files via Excel and MS
Access.
I was surprised to learn that MS Access will still lock these .csv files
even though the user only has read-only permission.
This effectively does two bad things. If a user keeps Access open through
the night, my job fails because the files are locked. Also, there seems to
be more and more contention problems between users of this data, when one of
them is using MS Access.
Is there any way to force MS Access to play nice with Excel concerning
multiple users of a read-only .csv file?