Cannt help you sorry.

Catherine Vallee
Cannaregio 4118
30121 Venezia
Tel +39 041 241 23 23
Cel +39 340 572 62 57


--- En date de : Lun 21.7.08, M. Fioretti <[EMAIL PROTECTED]> a écrit :

> De: M. Fioretti <[EMAIL PROTECTED]>
> Objet: [users] Does OOo Base "corrupt" Sqlite databases?
> À: [email protected]
> Date: Lundi 21 Juillet 2008, 22h24
> Greetings,
> 
> I am experimenting on Linux with OOo 2.3 Base and Sqlite3
> databases,
> using ODBC.  I have already managed to access from Base a
> test.db
> sqlite3 file I had created with a script, and to create
> forms and
> reports. Of course, when I saved the database, I got a
> wonderful
> "Test.odb" file, that is a zip archive containing
> xml files and other
> stuff.
> 
> The question is simply if it is "safe" to
> interact with the same .db
> file both from Base and from other applications. By
> "safe" I mean:
> 
> - if I close Base, modify the .db database with a script
> and reopen
>   with Base the .odb file, nothing bad happens
> 
> - all changes made via Base/odbc to the .db file are OK,
> that is
>   syntactically correct and don't corrupt the database
> in any way
> 
> - all of the above if Base and the other application, say a
> daemon or
>   cron job, access the database simultneously
> 
> My understanding is that everything should be
> "safe" as defined above,
> but of course I'd rather have confirmation before doing
> anything
> critical.
> 
> TIA,
>                       Marco
> -- 
> Your own civil rights and the quality of your life heavily
> depend on how
> software is used *around* you:           
> http://digifreedom.net/node/84
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


      
_____________________________________________________________________________ 
Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to