Ken, Thanks for reply, > I would start with APP A to determine after processing that the data that you > asked to be loaded is actually loaded. If it does not, then look into app A. > I think I need to add some more information here.
App B will be in running state, and whenever a write operation needs to be performed, it invokes App B. > If app A data load succeeds (and is correct in that all data loaded). > Run app B. If this errors out you more than likely have a query related > problem. Query is absolutely fine. A simple select on the table after the database table corrupt does not show some rows, which is expected to be there. I will post the simple schema and the actual SQL statements I am using so that might be helpful. -- Bharath On 3/17/08 8:16 PM, "Ken" <[EMAIL PROTECTED]> wrote: > > HTH, > Ken ----------------------------------------------- Robosoft Technologies - Come home to Technology Disclaimer: This email may contain confidential material. If you were not an intended recipient, please notify the sender and delete all copies. Emails to and from our network may be logged and monitored. This email and its attachments are scanned for virus by our scanners and are believed to be safe. However, no warranty is given that this email is free of malicious content or virus. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
