Isolating data access from the maintenance of that data

[Gryfphon]

Have experimented with the process of maintaining (add, delete, modify) a worksheet in a separate (book1.xls) project and accessing the same data via Connections, Data in another (book2.xls) project. The idea is that there are many read-only users and a few maintainers; the hope is to reduce conflicts between "readers" and "maintainers"; refreshing is expected to provide access to the most recent data as maintenance is performed. I'm trying to anticipate/avoid unforeseen pitfalls with this idea.

Sorry All ! Neglected to mention that workbooks are available to all on a network shared disk space. book2.xls Connects to book1.xls to access only one (1) worksheet. My experience so far, is that if book1.xls (which is referenced via Refresh from book2.xls) first and then open book2.xls, all proceeds as desired; updates are made and saved in book1.xls and book2.xls "sees" the changes via the Refresh. If, however, book2.xls opens first, then book1.xls can only open as "Read Only" which is the opposite of what is desired. Is there something that can be coded always allow book1.xls to maintain r/w access to the shared worksheet ?