Well, I am afraid it didn't work.
Somehow, the legacy_file_format info is not "sticky".
I did:
sqlite3
then in command mode:
PRAGMA legacy_file_format=ON;
then
ATTACH "d:\mydb.db" AS mydb;
then
CREATE TABLE TEST (id int);
if I then quit and return to sqlite3 and attach the database I just
created and issue the following command:
PRAGMA legacy_file_format;
I get the answer "0" (when it was "1" during the previous session).
This means that when I export my tables from Access to the ODBC
datasource of SQLite3, it does not keep the fact it has to write
"legacy format". This confirmed by the fact I can't read the database
on my Mac.
Did I do something wrong?
Thanks,
Alex
--
Alexander Lamb
[EMAIL PROTECTED]
On Aug 4, 2006, at 3:34 PM, Alexander Lamb wrote:
Ahah, I understood "PRAGMA" as an compile option :-(
That's why point 2 was not very clear (I am new to SQLite).
I'll do this right away!
Thanks,
Alex
--
Alexander Lamb
[EMAIL PROTECTED]
On Aug 4, 2006, at 3:27 PM, Gerry Snyder wrote:
Alexander Lamb wrote:
So it is not possible to create a database with the legacy file
format using the command line on Windows and SQLite 3.3?
Yes it is. Reread Dr. Hipp's point (2) below.
If I understand correctly, I need to grab the latest CVS version
of SQLite to have the 3.3 format disabled by default.
Yes, but you do not need to use the default. You just need to
issue the pragma command before creating the first table in the
new file. Reread Dr. Hipp's point (2) below.
The problem I see with that is that I am not a Windows developer
so I have no way of compiling the .exe and .dll
No need. That was just one of the suggestions.
On Aug 4, 2006, at 12:13 PM, [EMAIL PROTECTED] wrote:
Either (1) use the latest version of SQLite from CVS or (2)
run
PRAGMA legacy_file_format=ON;
prior to creating that first table in the SQLite database.
Hope this helps.
Sorry I was too lazy to correct the top-posting. The mish=mash may
be hard to read.
Gerry
