Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsVB SyntaxEnterprise DevelopmentDatabase AccessControlsCOMWin APICrystal ReportDeploymentGeneralGeneral 2
Related Topics
VB.NET / ASP.NETMS SQL ServerMS AccessOther Database ProductsMore Topics ...

Re: OLAF - Baffled by CreateTableFromRsContent



Tip: Looking for answers? Try searching our database.



You are accessing this site in a read-only mode. For full access to all member benefits, including message posting, please login or register. Registration is completely free, simple, and takes only a few seconds.

Login | Free VBMonster.com registration | Whole discussion thread

The message you are replying to and its parents are listed in the reverse order with the most recent posts first. This might not be the whole discussion thread. To read all the messages in this thread please click here.

Re: OLAF - Baffled by CreateTableFromRsContent

Webbiz20 Jul 2009 01:54
>> The "CreateTableFromRsContent" is suppose to create a
>> table from a recordset, correct?
[quoted text clipped - 34 lines]
>
>Olaf

Ah. That is why I could not see any changes when I removed the "True".
The table name still showed up in my Sqlist_master.

Thanks!

Webbiz

Schmidt19 Jul 2009 21:03
> 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

Webbiz19 Jul 2009 00:42
Olaf-

The "CreateTableFromRsContent" is suppose to create a table from a
recordset, correct?

If you set (temp table) as true, does this mean it goes away as soon
as the procedure exits?

If I want this table to remain available for other procedures,
wouldn't I simply leave off the 'true'?

Thanks.
Rick

Quick links:

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage




©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.