<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>ChrisEngineer's Activities</title><link>https://communities.bentley.com/members/173175df_2d00_cf2b_2d00_42dc_2d00_b123_2d00_bd7a5e87988f</link><description>ChrisEngineer's recent activity</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>.gpk file goes to &amp;quot;read-only&amp;quot; when accessed remotely</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/100330/gpk-file-goes-to-read-only-when-accessed-remotely</link><pubDate>Thu, 21 Aug 2014 18:46:51 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:cc0946d1-f75b-4a5f-a449-f8f471132352</guid><dc:creator>ChrisEngineer</dc:creator><description>&lt;p&gt;My company uses GEOPAK V8i and has multiple office locations connected by local servers that cache project files and then connect to the main servers at our headquarters. &amp;nbsp;Whenever a remote office collaborates with another office, typically headquarters, the .gpk file becomes read-only for everyone except the first person to activate the .gpk, until everyone closes out of their files. &amp;nbsp;Then a new &amp;quot;first person&amp;quot; can gain write privileges to the .gpk but all others are still read-only. &amp;nbsp;I thought the purpose of the .gpk was so that multiple users could all work on the same project at the same time. &amp;nbsp;We do not have this problem when multiple users AT THE SAME LOCATION access the .gpk - it&amp;#39;s only when two office locations access the .gpk. &amp;nbsp;We recently switched from Microstation SS2 to SS3 and have had this problem on both. &amp;nbsp;Has anyone else had this problem and found a solution?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>