Re: [RadiusNT] Server Access Table

Mike@NetDotCom ( (no email) )
Fri, 8 Oct 1999 09:11:40 -0400

Dale:

Boardtown support told me this:

The IEA scripts they received showed that the port column allowed nulls,
but, the port column was part of the primarykey and when using SQL 7.0
primary keys cannot contain columns that allow nulls. Hence a null is not
allowed as I am using SQL 7.0

Is this true?

Mike K

----- Original Message -----
From: Dale E. Reed Jr. <daler@iea-software.com>
To: <radiusnt@iea-software.com>
Sent: Thursday, October 07, 1999 5:30 PM
Subject: Re: [RadiusNT] Server Access Table

> "Mike@NetDotCom" wrote:
> >
> > I am on the phone with Boardtown now, their scripts don't match what the
> > RadiusNT manual states. Their scripts created the table to prevent nulls
in
> > the port field.
> >
> > The RadNT manual states the the port field can contain a NULL which
means
> > all ports. Or is the RaduisNT manual in error and you can't use a NULL?
>
> The old schema didn't allow NULLs (like 2.2). 2.5 and higher does
> allow/support NULLs.
>
>
> --
>
> Dale E. Reed Jr. Emerald and RadiusNT
> __________________________________________
> IEA Software, Inc. www.iea-software.com
>
> For more information about this list (including removal) go to:
> http://www.iea-software.com/support/maillists/liststart
>

For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart