What you are saying is true but so is the info that the programmers
gave. The programmers just could have been a whole lot more
informative about the CONSEQUENCES of detaching and reattatching.
The only reason to detatch is if you are not getting any new units and
in that case the old units would either have already been processed
and reported or your system really needs to be detatched and
reattatched. Detatching while you still have units, either in progress
or to do, WILL produce the effects you outlined.

On Thu, 8 Jul 2004 23:40:03 -0400, "Bill Barto" <nospam@noaddress>
wrote:

It might be too late for this warning but DO NOT DETACH FROM THE PROJECT.
When you detach from the project you will lose all WU's in the queue, all
work in progress and any completed WU's that have not been uploaded/updated.
This was really bogus information they gave us.

"Klaatu" <mutster8_nospam_@netscape.net> wrote in message
news:TRmHc.12131$ys6.2333@newssvr24.news.prodigy.com...

"July 8, 2004
We have moved the scheduling server to another machine in order to free up
CPU and memory for the DB server. Active clients will fail 10 times to
connect to the old scheduling server and then will self correct by
contacting the master URL. To force the correction right away, simply
detach and then (re)attach the project."