<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
</div>You don't want to update the node tables directly. You would miss out<br>
on the hook implementations. You need to create a node object and use<br>
node_save() to do it. You could manage this by creating a custom<br>
module to push and pull the changes to an external DB for the ms<br>
access entries via a hook_cron implementation. There may be a module<br>
already to do this but I don't know.<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>What are the hook implementations you mention specifically??</div><div><br></div><div>If the data tables are all updated correctly will drupal not see it as a node?</div>
<div><br></div><div>As mentioned we aren't programmers so this seemed like the easier option..</div><div><br></div><div>My concern with trying to write something to keep two sets of data "syncronised" is managing the whole syncronisation process and issues with changes happening on both sides causing a "split brain" scenario.. If both access interfaces are editing the same data this is reduced.. No different to why MySQL replication is not often attempted as master-master because the sync is not easy to do reliably..</div>
</div>