View Single Post
  #2   Report Post  
Posted to microsoft.public.excel.misc
Dave F Dave F is offline
external usenet poster
 
Posts: 2,574
Default Version Control on Excel Databases

Excel isn't really designed to do what you want to do. It's not a
collaboration tool, and doesn't handle multiple users well like a
conventional database. I suppose it's possible to time stamp when a change
is made to a workbook via a macro, but even there, that is easy enough to
circumvent, either on purpose or inadvertently, by not enabling macros upon
opening the workbook.

If you really need to be able to time stamp people's entries you need a
database, not an Excel spreadsheet.

Dave
--
Brevity is the soul of wit.


"Scott" wrote:

Hello,

I have a shared database set up in Excel where approximately 30 users
contribute data, weekly. Each user has a specific (and unique to others)
record they are responsible for. The database is set up on a shared LAN
drive. Each user has been instructed to update the database "in-place".
That is, not to take a copy of it, update their record and resave the entire
file back to the original location. This is obviously to maintain security
and version control.

Recently, we've heard complaints from some users that their data entered the
prior week "reverted" back to old data. A couple of reasons for this come to
mind:
1. The user did not save the workbook when they finished entering data.
2. A user did not update the database "in-place" and thus overwrote other's
records and possibily old data.
3. Some technical problem with excel and shared workbooks unknown to me?
4. Others perhaps?

Question regarding # 2. How do I prevent a user from saving a copy,
updating the record and rewriting of the database back to its location?

Regards