> The "CreateTableFromRsContent" is suppose to create a > table from a recordset, correct? Yes.
> If you set (temp table) as true, does this mean it goes away > as soon as the procedure exits? No - the Temp Keyword for Table Creation in SQLite-DDL means, that these tables are cleared up, as soon the underlying *Connection* goes out of scope. In your case that means, that these tables live as long as your App lives (since your Connection-Object is defined publically inside a *.bas-module - and only initiated once).
In case of a FileBased DB: Specifying Temp creates the Table in SQLite Temp-area - and in my wrapper-compile I've specified, that this Temp- area is hosted always in Memory - no matter if the underlying DB-connection is currently filebased. Specifying Temp=False means, that CreateTableFromRsContent will create a real table within your filebased DB, which is of course persistent then.
In case of an InMemory DB (which you are using in your Stock-Data-Application) it really does not matter, if you specify Temp=True or Temp=False (creating a "normal Table" or a Temp-Table), since the entire DB-Connection (and all the "normal Tables"-content) is already hosted entirely within memory.
> If I want this table to remain available for other procedures, > wouldn't I simply leave off the 'true'? No matter what you specify (in case of an InMem-DB) - the table remains open as long as the Connection is alive.
And as said, in case of a filebased DB (when specifying Temp=False) such created tables are persistent, even when you close the Connection.
Olaf
|