Consistently, though? The problems I've seen with MS Access
is that randomly you'll get 5000+ ms response times,
especially if you get someone else (besides RadiusNT) hitting
the DB.
> ----- Original Message -----
> From: Dale E. Reed Jr. <daler@iea-software.com>
> To: <radiusnt@iea-software.com>
> Sent: Tuesday, August 10, 1999 2:25 PM
> Subject: Re: [RadiusNT] Is this a RadiusNT bug?
>
> > ValNet Sysop wrote:
> > >
> > > We are still working around this problem by giving the user 2
> logins.
> > > Once they discover this it will be a real problem. We can not duplicate
> the
> > > problem on demand but the logs fill up fast when the user has a single
> > > login.
> > > Surely this is not a marketing feature for the Enterprise edition...
> >
> > My first recommendation is going to be to upgrade to SQL Server and
> > get away from MS Access. Although Access works OK, it can be the
> > cause of a LOT of problems, especially those that are time critical.
> >
> > Without actually getting more information about the problem, its
> > real tough to resolve. :( For example, what kind of typical
> > response times are you seeing from RadiusNT? You can run it in
> > -x15 debug mode to see.
> >
> > --
> >
> > 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
--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