First: Dump VB and use Delphi. Second (more seriously): try to find an interface that directly exposes sqlite. Actually, you may be able to get away with this with your current wrapper: try replacing the sqlite3.dll file with a new one and see what happens. I use a Delphi unit to interface with the DLL and while I don't get any new functions, I can now use newer SQL commands through the slightly older unit.
On 11/27/06, P Kishor <[EMAIL PROTECTED]> wrote:
On 11/27/06, RB Smissaert <[EMAIL PROTECTED]> wrote: > Just to clear up one thing that is not 100% clear to me. > When you are using SQLite on your machine is it true that you don't need to > have anything installed if you are using a VB wrapper dll. This wrapper can > Create, update, select etc. and nil else is needed. > > Now, if I am using this wrapper and there is a new version of SQLite out > what does that mean to me? I suppose nil, unless the author of the wrapper > brings a new one out that uses features of the new version of SQLite? I don't know the first V about VB, but your logic seems immaculate. Such is the peril of using a wrapper made by someone else. I live on a similar edge with Perl DBD::SQLite which has SQLite, the library, bundled in it. If I had my druthers I would compile my own, but I lost my druthers a while back... so I suffer the consequence of laziness. Its no big deal -- in my world, DBD::SQLite is reasonably current (keep in mind, not every x.x.y release of SQLite is a crucial upgrade). You could write to the author of your VB dll, buy her a beer or something. > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of P Kishor > Sent: 27 November 2006 20:59 > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Saving tables > > SQLite is the C library that does all the db magic. You have to > somehow get to that library, which you can do from a program written > in a variety of different languages, even GUI programs, or, from > another confusingly similar named program called sqlite or sqlite > shell. Since the jump from version 2 to version 3 of SQLite, the C > library, made the data incompatible between the two versions, the > version 3 of the shell is called sqlite3 usually... it uses the SQLite > library version 3.x > > Here is what I did (my comments in-line) > > > sqlite3 foo.sqlite > > # called sqlite3 with a db named foo.sqlite > # since foo.sqlite didn't exist at first, sqlite3 helpfully created it > > > CREATE TABLE bar (a, b); > > INSERT... > > # CREATEd a table and inserted a row into it. > > > .quit > > # got out in a hurry (that was a .dot command, specific to sqlite3, the > shell) > # time passed > > > sqlite3 foo.sqlite > > # this time foo.sqlite existed, so sqlite3 just opened it up > > > SELECT * FROM bar; > > # the table bar was there, and had my data in it. > > > > On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: > > > > I typed exactly what you typed there and i get > > SQL error: no such table: bar > > my command window doesnt have : "sqlite3 foo.sqlite" like yours > > > > > > > > > > > > P Kishor-2 wrote: > > > > > >>sqlite3 foo.sqlite > > > SQLite version 3.3.7 > > > Enter ".help" for instructions > > > sqlite> CREATE TABLE bar (a, b); > > > sqlite> INSERT INTO bar (a, b) VALUES (1, 'my mp3'); > > > sqlite> .quit > > > > > > .. time passes.. > > > > > >>sqlite3 foo.sqlite > > > SQLite version 3.3.7 > > > Enter ".help" for instructions > > > sqlite> SELECT * FROM bar; > > > 1|my mp3 > > > sqlite> > > > > > > > > > > > > On 11/27/06, sebcity <[EMAIL PROTECTED]> wrote: > > >> > > >> I created a table. > > >> I populated the table. > > >> I exited SQLite. > > >> Started SQLIte again. > > >> Typed "select * from <table name>". > > >> ANd it tells me no such table exists?? > > >> > > >> > > >> > > >> Igor Tandetnik wrote: > > >> > > > >> > sebcity <[EMAIL PROTECTED]> wrote: > > >> >> Im new to SQLite, After you create your tables how do you save them > > >> >> so they are permenently there? It might be a dumb question but i > cant > > >> >> find the answer anwhere?! > > >> > > > >> > They are "permanently there" from the very moment you create them. > All > > >> > changes are written to the database file when a transaction is > > >> > committed, or at the end of every statement if you don't open any > > >> > transactions explicitly. > > >> > > > >> > Igor Tandetnik > > >> > -- Puneet Kishor http://punkish.eidesis.org/ Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/ Open Source Geospatial Foundation https://edu.osgeo.org/ ------------------------------------------------------------------------------------------------------- collaborate, communicate, compete ==================================================== ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
-- Isaac Raway Entia non sunt multiplicanda praeter necessitatem. http://blueapples.org - blog http://stonenotes.com - personal knowledge management
