one could store the database file as a custom property then when needed, could extract the file from the property, and save it as an anonymous temporary file, using *the tempname*. Then delete that file when the operation or application is done.
*Examples: * the tempName put the tempName into testDataPath Use the *tempName* function to find an appropriate place to put a temporary file. I've done this too, in a work-around concerning decoding encrypted audio files in Rev. On 27 October 2011 20:53, James Little <littlejam...@mac.com> wrote: > > Richard Gaskin wrote: > > > With LiveCode you have a wide range of formats available. For large > tabular data sets you can use SQLite, define your own format using simple > text files, store arrays using arrayEncode, or even use custom properties > stored in a stack file (a favorite of mine since it lets me use name-value > pairs very conveniently. > > > > Sarah Reichelt's helpful article on saving data from a standalone may be > helpful: > > <http://livecodejournal.com/tutorials/saving_data_in_revolution.html> > > > > Is it possible to store a SQLite file as a custom property in LC? > > My reason is to preserve the file as proprietary data. I guess that I > would need to be able to access and to store data with SQL queries in > private way. > > I would appreciate any advice or pointers to reference info. > > Thanks, > > Jim L. > > > > > > > _______________________________________________ > 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 > -- Stephen Barncard San Francisco Ca. USA more about sqb <http://www.google.com/profiles/sbarncar> _______________________________________________ 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