Is your database still in the corrupted state? If so issue the following command:
PRAGMA integrity_check It will return either OK if it doesn't find any errors or a list of error messages. That won't discover exactly what caused the problem but it might point you in the right direction. In particular, if it returns OK, then at least you will know the database didn't get corrupted. Pete lcSQL Software <http://www.lcsql.com> On Fri, Oct 5, 2012 at 12:59 PM, Dr. Hawkins <doch...@gmail.com> wrote: > On Thu, Oct 4, 2012 at 8:43 AM, Bob Sneidar <b...@twft.com> wrote: > > Richard, barring anything your app could have done to wipe the data, and > barring a damaged database file (a possibility if the > >physical media took a hit) there is only one thing left. Someone hacked > into your database and altered the data. How is your app > >accessing the data? Is the access to the database encrypted? > > The database was on my iMac, the same3 one with which I was accessing > it, behind a router, behind a dsl "modem"--so access never left the > local machine. > > -- > Richard E. Hawkins, Esq. > (702) 508-8462 > > _______________________________________________ > 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 > _______________________________________________ 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