PL Beta 1

在经过了长达两的月的马拉松式谈判，云少最终情定CTE！他是昨日在为了配合PL Beta 1的推出而在金马酒店举行的发布会上正式作出这样的宣布。他也郑重的向传媒否认他曾经有转会的心意。他说身为OI部门高级主管，他由头到尾都对CTE一条心，从来没有跳槽的意图，希望传媒以后不要在乱乱写。

云少在发布会上向来自全世界超过70个国家的传媒代表展示了CTE最新的产品- PL Beta 1的多项功能。他也向传媒表示由于是Beta版本，所以有些功能不会出现在最终的正式版本。而这次Beta版主要是锁定给跟CTE有密切关系的公司来进行测试的。也因为这样所以公众暂时还不能从CTE网站上下载来测试。根据云少提供的时间表，PL的正式版本将在今年第三季内推出。他表示到时CTE会为此进行空前绝后的宣传活动，并会在全世界超过100个国家同步发行。预料漏夜排队买视窗95的情形应该会再次出现。云少甚至扬言PL将会在一年内占据CTE全年总赢收的3成以上!

部落格

这个部落格沉寂了一段时间（经过一连串的离职事件）
终于有点生气了，ctesoftware也进入了风平浪静的阶段 （希望好景常在）
突然间想起一句话，暴风雨来临前总是风平浪静的 :O
算了，别想酱多
最近发现到两个程式员的部落，蛮不错的,好东西与大家分享
關於電腦
程式設計員的創業生涯
里面有一片关于"Support, Salesman & Programmer的關係"的文章 - 誤會很深
得空就看看，不懂你们认同吗

Standard Service System

One customer bought his PC to reinstall the 3A this afternoon. CAT told me she couldn’t find their Service SYS in the server. Since the person in charge for the Service SYS was not coming today, I told her I also not able to do anything about that. The only thing I could do for her was going to ask Mr. Wu where is the standard Service SYS? But very surprising that he answered me that there is NO any standard SYS for the Service SYS. All the Service SYS we sold to the customer were modified from the Mantruck Service SYS. Then Mantruck Service SYS is considered as standard already. OMG! How come such thing can be happened? Look like Yee Peng really needed to do something about that.

Anderson Loo
Access Team Member

Exporting the PO

Last week "SureWin" told me that Rovski was complaint about the PO was unable to export to Microsoft Excel properly. After I checked the standard version, I found that not only their version was not working properly, but the standard also. The worst part was the PO also not able to be printed in snapshot. I was quite surprise about it. I guess Rovski was the first customer who tried to export the PO. No other customer did that before. If not, that is impossible that until today we still don't know such bug exists.

In the beginning, I was suspecting that the sub report makes the exporting not working properly. But after I tried to redesign the report, I found that this is not the true, the sub report didn't bring any problem to the exporting. Look like the problem was in the coding part and not in the design part. I tried to run the exporting in debug mode and this time I was able to know where the code was stopped. Look like the problem was caused by some "old programming style". I think I needed to rewrite the "style" in order to fix the bug. Finally, the PO was able to export into the Excel after I modified the code.

I upgraded the standard and this was the first time we upgrade our PO since two years ago. Anyone who needed to solve this problem, you can try to import the "rptPoPrint" from the latest PO version 80. Good luck.

Anderson Loo
Access Team Member