I updated my Delphi 6 to SP2. I am not sure if the update pack did this,
but I have not installed anything Delphi related since then.

I cannot open the CommandText property editor for a TSQLDataset. I click
and click, but nothing happens. The SQL editor for IBX works. The
CommandText for ADO works. And so on... but TSQLDataSet doesn't work. Is
it just me?? Any idea what is broken? :(

Doesn't open even if you have SQLConnection property set ?
With dbExpress you need to have  connection set prior to open the
Commandtext editor.
HTH,
Emeli

In article <3C868969.71257...@borland.com>, emarcon...@borland.com
says...

You are right. We have a multi-developer shop here using Interbase.
Since IB supports only physicial drive letters, not subst drive or
loopback drive connections, we all have different paths to our DB. Last
guy to use datamodule had different path. :(

What is strange is how this behavior is inconsistent across components.
Not only do we have different kinds of SQL editors, but now they even
behave differently.

This is the only component I know that requires a valid connect to the
database in order to edit your SQL (or CommandText or whatever it's
currently called). x-(  Borland, WHY??

In article <MPG.16f053cf496d06d0989...@newsgroups.borland.com>,
k...@millerdevelopment.info.nospam says...

        For better or worse, subst seems to work for IB.  Before you're
tempted to use this, keep in mind that IB requires physical drive
letters for a reason (to prevent two servers from trying to access the
same DB file concurrently) and you tak this responsibility on your
shoulders when you work around this.

        Heck, I've seen different SQL editors for the *same* component.  :)  
One of the third-party tools I installed (not even sure which one)
replaced the BDE's SQL editor with a much nicer one.

        -Craig

--
 Craig Stuntz (TeamB) Vertex Systems Corp. Columbus, OH
     Delphi/InterBase WebLog: http://delphi.weblogs.com
     InterBase PLANalyzer (Free IB optimization tool):
          http://delphi.weblogs.com/IBPLANalyzer

In article <MPG.16f06dc22fe07423989...@newsgroups.borland.com>,
cstuntz@no_spam.vertexsoftware.com says...

It's strictly for development purposes. Subst under XP works differently
than all previous Windows systems. I should have qualified that in my
first post. I guess Microsoft changed the rules on how a subst drive
appears. It is no different, OS wise, than a network share connection,
which IB doesn't like.

Raize's does that, but I don't like theirs. Just give me a good old
fashioned TStrings editor with the ability to pop into the code editor
for increased editing power. :) OR, bring back the old BDE SQL editor
with the tabbed interface, but give it the power handle paramterized
queries and column aliasing. (Many people didn't realize it did support
table aliasing.)

Back to TSQLDataset requiring a valid database connection. I am very
tempted to report this as a bug. There can easily be occassions when I
don't have access to the database at the moment, like when on the road,
and I need to be able to edit my CommandText. This new requirement is
too restrictive.

What do you think? A bug?

In article <MPG.16f1468fa6cdc59e989...@newsgroups.borland.com>,
k...@millerdevelopment.info.nospam says...

        A feature request, and not a bad one.

        IMHO,

        -Craig

--
 Craig Stuntz (TeamB) Vertex Systems Corp. Columbus, OH
     Delphi/InterBase WebLog: http://delphi.weblogs.com
     InterBase PLANalyzer (Free IB optimization tool):
          http://delphi.weblogs.com/IBPLANalyzer