Its actually a fix to a kludge we added when we ran into a problem
with MS Access supporting the NULL value for it. NULL is the correct
value for all databases now. I'll check the docs to see if it was
updated to reflect that.
> Dale can you comment as to whether this was changed by design or accident,
> Why there are no notes on this, and whether we could have both modes
> supported for consistency purposes. I want to upgrade but the databases are
> so different now there is no backwards compatibility between 2.2 and
> 2.5.124. The upgrade must be done in one foul swoop. I was kinda hoping I
> could make 2.5 changes to the 22 database but still use 2.2 until we were
> ready for the switch of executables.
You can use a simple query to update it:
Update Services Set TimeLeft = NULL Where TimeLeft = -9999
Although I thought it did, it doesn't look like 2.5 is respecting the
-9999. I thought it still did, and that is the main reason why there
wasn't a big note about it.
-- Dale E. Reed Jr. (firstname.lastname@example.org)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com