This is a good example of how sqlYoga can help. You could create two database objects, query the disk based database for all the records in a table using the disk based object, then insert the records using the memory based object. If the databases are not very large it shouldn't take that long.
But I think your idea of using a file copy method is the best way. I used to do that with the Spiceworks database because the Spiceworks system would periodically open the database and since it is really a single user system opening it directly could cause problems with Spiceworks. I just did a simple file copy and worked with the copy. Bob S > On Oct 17, 2015, at 10:12 , Glen Bojsza <gboj...@gmail.com> wrote: > > Essentially, I want to keep the database in its original form / content. > > While the user is running the app I want to be able to make changes to the > database knowing that the changes are done in memory and will not be > written to the original database. > > I could duplicate the database to a folder on the disk and then later > remove it but if I can do it just in memory and it automatically cleans out > after the user quits the app then it would be more convenient. > > For example, if I don't the user to be able to look into the database > (which I believe can be done if it is written to disk) using in memory > would be the way to go...true? > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
