I've read lots of reasons for an Excel sharing violation...

---) Certain Novell software
---) Insufficient folder rights
---) Antivirus scanned the temp file Excel uses

The first two culprits can be easily eliminated, but #3 is a must for
security, according to security folks. No safe way around it.

Therefore, Excel is prone to commit a sharing viloation, it's just a
matter of when. Problem is, such an error locks out other users and
the original user must somehow re-enter changes they made from the
copy Excel made of thier file. This is unacceptable in a busy
department.

1) So, being temp files ARE scanned, are shared Excel files even
reliable?

2) Do any of you employ shared files for yourselves or for clients
dispite the above information?

3) Do any of you recommend AGAINST shared files in Excel?

Thanks,
Robert

Windows 2000
Excel 2002
McAfee VirusScan v4.5.1
McAfee virusScan Enterprise v7.0.0

Excel is not a database program, so its sharing is not that good.

I would recommend an excel frontend to an access\sqlserver backend if the
sharing is really just data.

Charles
______________________
Decision Models
FastExcel 2.1 now available
www.DecisionModels.com

"Robert" wrote in message
om...
I've read lots of reasons for an Excel sharing violation...

---) Certain Novell software
---) Insufficient folder rights
---) Antivirus scanned the temp file Excel uses

The first two culprits can be easily eliminated, but #3 is a must for
security, according to security folks. No safe way around it.

Therefore, Excel is prone to commit a sharing viloation, it's just a
matter of when. Problem is, such an error locks out other users and
the original user must somehow re-enter changes they made from the
copy Excel made of thier file. This is unacceptable in a busy
department.

1) So, being temp files ARE scanned, are shared Excel files even
reliable?

2) Do any of you employ shared files for yourselves or for clients
dispite the above information?

3) Do any of you recommend AGAINST shared files in Excel?

Thanks,
Robert

Windows 2000
Excel 2002
McAfee VirusScan v4.5.1
McAfee virusScan Enterprise v7.0.0

Hi Charles
if it really only data entry I would even input it directly in Access
(and use Excel maybe as reporting tool). But just a matter of personal
taste :-9

totally agree with you that 'sharing' is not a good idea. also I found
this 'feature' quite buggy


--
Regards
Frank Kabel
Frankfurt, Germany


Charles Williams wrote:
Excel is not a database program, so its sharing is not that good.

I would recommend an excel frontend to an access\sqlserver backend
if the sharing is really just data.

Charles
______________________
Decision Models
FastExcel 2.1 now available
www.DecisionModels.com

"Robert" wrote in message
om...
I've read lots of reasons for an Excel sharing violation...

---) Certain Novell software
---) Insufficient folder rights
---) Antivirus scanned the temp file Excel uses

The first two culprits can be easily eliminated, but #3 is a must
for
security, according to security folks. No safe way around it.

Therefore, Excel is prone to commit a sharing viloation, it's just a
matter of when. Problem is, such an error locks out other users and
the original user must somehow re-enter changes they made from the
copy Excel made of thier file. This is unacceptable in a busy
department.

1) So, being temp files ARE scanned, are shared Excel files even
reliable?

2) Do any of you employ shared files for yourselves or for clients
dispite the above information?

3) Do any of you recommend AGAINST shared files in Excel?

Thanks,
Robert

Windows 2000
Excel 2002
McAfee VirusScan v4.5.1
McAfee virusScan Enterprise v7.0.0