Try notepad+

No Problem at all: #ifndef HEADER_XY #include 'HEADER_XY.H' #endif In HEADER_XY.H must - of course - written been #define HEADER_XY

Hi Charlie, AFAIK you have to connect RTS / CTS, this is a hardware-Handshake. Have a Look to Wikipedia for an Explanation Greetings, Klaus

There are 2 versions, one from Schubert, one from Bach / Gounod.. Ave Maria - Bach- Violin - YouTube[^]

Jörgen Andersson wrote:

Almost forgot, Varchar has a limit of 32767 characters instead of 4000.

The Limit was not 4000 characters but 4000 Bytes (new: 32767 Bytes)

Yes, it WILL use another font, even without you telling it to do so: Weiterleitungshinweis[^]

Well - Clippy IS back - sort of ... clickety[^]

Joan Murt wrote:

ultra-800kb download speed

Me think my phone has a faster connection ... :sigh:

Thanks for your thoughts, Jörgen. Of course the results differ, and to achive the correct result, one have to write

AND NVL( F.OtherID, 1 ) = 1

Quote:

My personal pet peeve is that a field should always have the same name everywhere in a database just like the ISO standard says

Don't know where you read this, but it cannot be right ... Even in my original simple example you have two addresses in tho ORDERS table, so there is no chance in having 'the same field always the same name'. Maybe you meant that a field with the same MEANING should have always the same name, like CUSTOMER, FORWARDER etc. ?

Wrong - it's the OPPOSITE side that can be NULL, as in O.Forwarder = F.ID(+) Here, O.Forwarder my be NULL, but F.ID can NEVER be NULL (it's usually the primary key)

Well - the title should be clear enough, and I presented JOIN syntax and WHERE syntax, expressing my worry about noone seems using WHERE. THEN I asked for arguments - obviously (I thought so) WHY noone is using WHERE syntax, and NOT to support my preference. In other words: Are there any points (other than preference) to not using WHERE syntax ??

Mycroft Holmes wrote:

Nope, I call them Oracle joins

Yeah - a really qualified Response ... I ask for arguments, an your resposne is

Mycroft Holmes wrote:

I will [...] have a short, sharp discussion with the dev that uses it

THIS is my Intention - to have a DISCUSSION about it ! But you have obvoiously no arguments, but prejudices against it - not the ideal base for discussions. What would be your arguments in a discussion with your developer - do you even have any arguments ? Note: I asked politely for arguments for - or against - my preferation, because (as every of us) I want to improve my abilities, and also to give some impressions to SQL newbies to decide what to do, and not to do. So ... HAVE VOU ARGUMENTS, or are you just felt to open your mouth ... ?

I quite don't understand why noone is using the WHERE-Syntax for table joining ... I always see something like

SELECT O.Order_No, C.Address, F.Address
FROM Orders O
JOIN Address C
ON O.Customer = C.ID
JOIN Address F
ON O.Forwarder = C.ID

For me, the most irritating thig is the spreading of table names and aliases all over the Statement. I prefer

SELECT O.Order_No, C.Address, F.Address
FROM Orders O, Address C, Address F
WHERE O.Customer = C.ID
AND O.Forwarder = F.ID

- It's shorter - All table names and aliases are together Arguments, anyone ?

What a waste of time - whoever wins, it's nothing comparable to the german half final

Well - sometimes 'home field advantage' simply means: You can go home by bus ;P

Nothing funny: http://www.openelectrical.org/wiki/index.php?title=IP_Rating[^]

http://www.youtube.com/watch?v=PclufM9OMcw[^] :laugh:

This will not help you if you are comparing two variables ...

In C / C++ the IDE cannot catch it, because it as an absolut correct statement ! Ever seen the simple strcpy() function:

void strcpy( char *source, char *destination )
{
while (*destination++ = *source++ )
;
}

Fire up any text editor, compile the code below as pure C and you have what you asked for ...

#define IF if (
#define THEN ){
#define ELIF } else if (
#define ELSE } else {
#define ENDIF }
#define IS ==
#define EQUALS ==