Re: SQL Strangeness

John,

If you open everything via the RSE view, I can understand your viewpoint.
But if you open the source via the Object Table rather than the RSE tree
(which is how I work), it can be very difficult to determine which
connection was used to open a member. This is also true if you use
Ctrl+Shift+A to open one, but then the properties view won't even give a
clue to the connection used. I don't know where, but having an indication
somewhere of the connection used to open a member would be nice. I think
adding a prompt for the connection to compile a member would be
overwhelming to most folks.

That said, this is not the place to request a feature. Someone would have
to enter an RFE. I would but it's not been that often that I screw up.
When I do, it usually doesn't take me too long to realize I've opened a
member via the wrong connection.

Michael

wdsci-l-bounces@xxxxxxxxxxxx wrote on 01/08/2014 01:00:03 PM:

----- Message from "Voris, John" <john.voris@xxxxxxxxxxxxx> on Wed,
8 Jan 2014 16:52:03 +0000 -----

To:

"wdsci-l@xxxxxxxxxxxx" <wdsci-l@xxxxxxxxxxxx>

Subject:

[WDSCI-L] SQL Strangeness

For the WDSC group,
I just spent several hours trying to determine why a compile would

not work from RDi. Turns out it was trying to compile under the
wrong connection. It just uses the connection used to open the
source. In my case > the connection I opened the source under
allowed editing the source, but not compiling correctly. It would be
useful if the compile menu or prompt dialog displayed or allowed
selecting a connection for the compile.

. . . I don't always remember to set that field as it is usually

what I want, but I probably opened it last week, and didn't
remember. I am asking for a new feature here.

Sounds like you are requesting flexibility that is just not necessary.
For those new programmers coming from SEU who find RDi/RDp/WDSC just
too complex, another popup screen to confirm something that should
have been set before editing your source seems like an excessive
double-check to me. (Even I who have a huge amount of members open
in RSE Remote System Explorer, can see the filter and the connection
I am using if I scroll up far enough.)

Am I missing something ?

- John Voris