Reply to thread

Message

<blockquote data-quote="Zasurus" data-source="post: 530226" data-attributes="member: 26856">No I understand. And I disagree. It MAY be possible to crate a &quot;multi-seat&quot; system on a SQLite db structure for ONE application but as &quot;aj1405&quot; pointed out bellow SQLite does completely lock the complete DB file during read/write operations making it next to impossible to use with more than one application at once.Don't get me wrong I understand what you mean by it not being the complete solution due to the system needed to make sure one doesn't write over the others changes and that if one made a change the others would need to be constantly checking for those changes to be up to date (especially before making there own changes) for me multi-seat is a second problem and something I wanted for the future as I currently don't have more than one PC accessing this DB (don't get me wrong I DO want to be able to do this soon! ;-)).I was only trying to say that out of the choice of DB types (file or full server SQL) I would like it to swing towards server SQL so it can ALSO be access (maybe only for reads and a few writes to its own columns/tables) with db like access and sqlite they don't handle this very well (or at all! ;-)).Hope this makes more sense? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused&nbsp; &nbsp; :confused:" loading="lazy" data-shortname=":confused:" /> <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />I didn't mean to upset you fforde <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite10" alt=":oops:" title="Oops!&nbsp; &nbsp; :oops:" loading="lazy" data-shortname=":oops:" />Regards,Zas</blockquote>

[QUOTE="Zasurus, post: 530226, member: 26856"] No I understand. And I disagree. It MAY be possible to crate a "multi-seat" system on a SQLite db structure for ONE application but as "aj1405" pointed out bellow SQLite does completely lock the complete DB file during read/write operations making it next to impossible to use with more than one application at once. Don't get me wrong I understand what you mean by it not being the complete solution due to the system needed to make sure one doesn't write over the others changes and that if one made a change the others would need to be constantly checking for those changes to be up to date (especially before making there own changes) for me multi-seat is a second problem and something I wanted for the future as I currently don't have more than one PC accessing this DB (don't get me wrong I DO want to be able to do this soon! ;-)). I was only trying to say that out of the choice of DB types (file or full server SQL) I would like it to swing towards server SQL so it can ALSO be access (maybe only for reads and a few writes to its own columns/tables) with db like access and sqlite they don't handle this very well (or at all! ;-)). Hope this makes more sense? :S :D I didn't mean to upset you fforde :ooops: Regards, Zas [/QUOTE]

Verification