Here's a message I got a couple of months ago on how to find a
     listserv

     Ian.

     I don't know the address of the Oracle list server, but I know how you
     can find out. Try sending a message to listserv@searn.sunet.se
     containing the command following command in the message body:

     lists global /oracle

     In fact, if you just send the message
     lists global

     It'll send you back a reply detailing all the lists it knows about
     (you may get a bit overwhelmed though!).

     HTH
     S&y
     Sandy Henderson
     HarperCollins Publishers
     Glasgow, Scotland, UK

     >>>>>>>>>>>>>>>
     Thanks in advance,

     Bill Palechek

     <<<<<<<<<<<<<<<



______________________________ Reply Separator _________________________________
Subject: Another MS SQL Server question
Author:  ,SYBASE-L@UCSBVM.ucsb.edu (Dave Clark) at ~INTERNET
Date:    6/30/97 9:27 AM


Hi,

First, thanks for the responses to my first question; changing the sort
order does the trick.  Since we are just beginning the port of our product
to the MS platform, it was not a big deal to do a re-install.  I still
question the sagacity of making the default sort order one in which
WHERE au_lname = 'm%' return 'McDonald', etc., but whatever.

I bought Microsoft SQL Server Unleashed to help me answer other questions,
but if anyone has another recommended book, I'd like to hear.

I do, unfortunately, have another question that I can't find the answer to.
Again, apologies; if someone knows of a MS SQL Server list and lets me know,
I'll take these questions there.

In the meantime:

We run on Sybase and Oracle currently.  In our Sybase version, we make use
of system defined data types.  We have a host of queries that for a
variety of reasons do a join involving two different user defined types.
The underlying system types are char(12) and char(50).  In Sybase - no
problem.  But in MS I get:

--Msg 305, Level 16, State 1, Server MVNTPC133, Procedure
infsys_montage_group_code_ti, Line 16
--The column 'list_code' (user type:List_Code) is joined with
'infsys_action_code' (user type:Infsys_Action_Code).
--The user types are not compatible:  user types must be identical in order
 to join.

This implies that even if the underlying types were both char(12), for
example, that this error would still occur.  And it does - I just checked.

Since I can do a join involving fields that are defined directly as
char(12) and char(50), I must conclude that MS is too brain dead to check the
underlying system datatypes for join compatibility.

Does anyone know a way to tell MS to look at the underlying types, or will
I be forced to abandon user defined types in our MS SQL Server version?

Thanks,
Dave Clark