Tim

Responding to the post by Dirk I suddenly thought wouldn't it be easier to track down the source or errant temporary tables if their name contained the name of the query that created them. I don't know how feasible that is so over to you.

Roy Lambert

Roy,

<< Responding to the post by Dirk I suddenly thought wouldn't it be easier
to track down the source or errant temporary tables if their name contained
the name of the query that created them. I don't know how feasible that is
so over to you. >>

What name in particular did you have in mind when you say "name of the
query" ?  Are you talking about the TDBISAMQuery component ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> What name in particular did you have in mind when you say "name of the
> query" ?  Are you talking about the TDBISAMQuery component ?

Nup, he meant sometihing like this ...

"SELECT D.Id, D.Description, D.Path, D.Params, D.StartFolder, D.Notes,
D.ShowDialog, D.Favorite, D.LastUsed, D.UsageCount FROM Document D WHERE
D.Id IN (SELECT DISTINCT D2.Id FROM Document D2 LEFT JOIN DocumentCategory
DC2 ON D2.Id = DC2.DocumentId LEFT JOIN Category C2 ON DC2.CategoryId =
C2.Id WHERE C2.Selected = True) OR D.Id NOT IN (SELECT D3.Id FROM DOCUMENT
D3 INNER JOIN DocumentCategory DC3 ON D3.Id = DC3.DocumentId)".dat

;-P

Happy New Year!!

--
Best regards

Steve

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:D2A6E041-29C9-4BF5-BBDD-0158DF43F0FF@news.elevatesoft.com...
> Roy,
>
> << Responding to the post by Dirk I suddenly thought wouldn't it be easier
> to track down the source or errant temporary tables if their name
> contained the name of the query that created them. I don't know how
> feasible that is so over to you. >>
>
> What name in particular did you have in mind when you say "name of the
> query" ?  Are you talking about the TDBISAMQuery component ?
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Steve


Very good try Steve but only slightly wrong Tim was much more accurate when he said the TDBISAMQuery component's name because that's what I was thinking. I know it would be of no help to those who simply drop the component on a form and don't rename it but that's life.

Roy Lambert

Roy,

<< Very good try Steve but only slightly wrong Tim was much more
accurate when he said the TDBISAMQuery component's name because that's what
I was thinking. I know it would be of no help to those who simply drop the
component on a form and don't rename it but that's life. >>

The other problem is that of sub-queries and how to transfer the name around
everywhere.  I'm afraid this one might have to wait until there's a day with
nothing to do.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>The other problem is that of sub-queries and how to transfer the name around
>everywhere. I'm afraid this one might have to wait until there's a day with
>nothing to do.


Presumably about the same time the moon changes colour to blue?

Roy Lambert

Roy,

<< Presumably about the same time the moon changes colour to blue? >>

Hopefully, sooner than that.

--
Tim Young
Elevate Software
www.elevatesoft.com

> The other problem is that of sub-queries and how to transfer the name
> around everywhere.  I'm afraid this one might have to wait until
> there's a day with nothing to do.

That's where Steve's file naming convention would do the trick.  

Seriously though - another problem you may have is 2 seperate forms /
datamodules with the same named query open at the same time.

I guess one way to get around the subqueries might be to append a number to
the end of the filename, so if their were 3 subqueries within a query called
MyQuery, you could have MyQuery1.dat, myquery2.dat and myquery3.dat. This
still wouldn't get you around the problem with multiple forms/dm's though.

However... as for waiting until theirs a day with nothing to do, I like the
sounds of that.... I'm hanging out for Tim to release something else instead
first.  

Cheers

Adam.