🚀 go-pugleaf

If query2 uses another connection than the one used to create the table it
doesn't see the table. Make sure you use the same connection.


"bmkiss67" <bmkiss67@aaahawk.com> escribi� en el mensaje
news:3e159b1a@newsgroups.borland.com...
> It's a #temptable.  I first create it, load it with data, modify the data,
> select data, and then execute it all with a execsql command in query1.
> Right after that I try to perform a different select on it with query2.
> Query2 returns the error that #temptable does not exist.
>
> "Ferran Barba" <ferran.barba@sifbm.com> wrote in message
> news:3e1543ae$1@newsgroups.borland.com...
> > What kind of temp table are you using (and in which database)?
> >
> > I'm asking this because if you create a temp table in SQL Server using #
> > (like CREATE TABLE #tempTable ...) and you close the connection after
> > creating it the table gets lost because it is a local temporary table.
If
> > you create a temp table using ## instead of # the table is accessible
for
> > all the user and gets deleted when all the users close the connection to
> the
> > server. I only know about SQL Server.
> >
> > If you create a temp table without # or ## (that is, a normal table),
> maybe
> > you have some king of access rights?
> >
> > "bmkiss67" <bmkiss67@aaahawk.com> escribi� en el mensaje
> > news:3e146d0b@newsgroups.borland.com...
> > > I have a temp table that I create on the fly and modify a bunch of
data
> in
> > > and then I run a query against to fill a report out.  When I did this
> > > originally I did it using the BDE.  I am in the process of switching
to
> > ADO.
> > > The problem I am having is that I have a second query I run against
the
> > temp
> > > table, but the query can't see the table.  Any suggestions?
> > >
> > >
> >
> >
>
>