Claus, Glad my sister represented herself and our family well. :-)
Here are some short answers to your questions: Yes, PRC could deploy from the test (dev) machine to the production machine. And "un-deploy" instantly if indicated! And yes, there are "project management" aspects such as estimating, tracking time, resource reporting (backlog by individual or type of project, overdue, etc.). And yes, it indicates clearly the change made to each program/component. There is a split-screen compare utility called KNIT (written by that same sister!) that makes this very easy to see. I don't think anyone ever prints it onto paper, but you could, of course. Hope things are warming up in Denmark - let me know if you have any more questions, either for the group or e.mail me directly at [EMAIL PROTECTED] Regards, Susan Joslyn >AD WARNING: Following is a blatant PRC brag and sales pitch thinly Disguised >as a technical discussion of its approach. (But I will stick with the >main technical differences ... unless you want more, then e.mail me!) He he... nvm the bad disguised shameless ad, your product looks cool, last year we had the pleasure of being educated a bit in SB+ by Susan's sister, and she also told us some good things about PRC :-) If I have an 8 user developer machine running linux + uv 10.1 and a 75 user production machine running linux + uv 10.1 will PRC then be able to deploy from the test machine to the production machine ?? If its project oriented, can you use it to keep track on status for a project like time used etc etc. ?? and when a project is finished can you write out all source code nicely on paper and also make a report on all the changes ?? We could seriously use a product like that! best regards from deepfreezing denmark Claus Derlien -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
