SQLite itself supports reading SQL and SQLite stmt/commands from a file, so the equivalent to the piped SQL would be
sqlite3 foo.db ".read bar.sql" -Clark ----- Original Message ---- From: Josef Hlawatschek (JT) <[EMAIL PROTECTED]> To: sqlite-users@sqlite.org Sent: Friday, May 5, 2006 12:28:38 AM Subject: RE: [sqlite] SQLITE3.exe from Windows CMD That did the trick. Thank you very much! Kind Regards Josef -----Original Message----- From: Arjen Markus [mailto:[EMAIL PROTECTED] Sent: 05 May 2006 08:56 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] SQLITE3.exe from Windows CMD Josef Hlawatschek (JT) wrote: >Hi, > >I want to use SQLITE3.EXE to run automated reports in Windows. I use an >init file to load parameters and a SQL script file. All goes well until >the SQL script has been executed, then the SQLITE3.EXE command prompt >appears. The command prompt only closes once you manually type in >".exit" or ".quit". I have tried to add the ".exit" to the init and SQL >script file and it still does not close automatically. > >I do not need to programmatically connect to the SQLITE DB, so I would >like to keep it as simple as possible. > > Why not use a pipe: - Put all commands in a file, say, sqlite.cmds - Run SQLite3.exe with the following command: > sqlite3.exe < sqlite.cmds That should work. Regards, Arjen ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This e-mail and its contents are subject to the Telkom SA Limited e-mail legal notice available at http://www.telkom.co.za/TelkomEMailLegalNotice.PDF ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
