发帖求思路
小弟用PB做了个订单上传的软件，用于公司的各销售人员向服务器上传自己的订单，用的是数据管道。
现在主管要求添加如下功能：
每个订单都有个Complete字段（Y/N）来标识订单填写是否正确。当订单上传时，Complete默认是Y，服务器端会有专门人员来审核订单，如发现订单有错，则将该字段改为N。
销售人员需要从服务器中搜索自己上传的那些审核未通过（即Complete为N）的订单，并下载到本机上覆盖原订单，修改后重新上传。
订单中有专门一列add_emp来标识不同的销售人员，即销售人员自己的编号。
小弟接触PB时间不久，不知红字部分功能如何实现，望指教～
[解决办法]
在你软件上 写个TIMER事件：用游标，做下面检索
SELECT ooxx into :ls_OOXX FROM 订单表 where add_emp = 当前销售 and Complete =N
检索结果放到一个数据窗口里，这样那边有审核没通过的当场就可以弹出列表了。
审核没通过，订单信息没变，不涉及到覆盖啊，根据列表改下本地订单表状态就好了，默认是Y 改成N
是这个意思不？
[解决办法]
Description
Executes a pipeline object, which transfers data from the source to the destination as specified by the SQL query in the pipeline object. This pipeline object is a property of a user object inherited from the pipeline system object.
Controls
Pipeline objects
Syntax
pipelineobject.Start ( sourcetrans, destinationtrans, errorobject
{, arg1, arg2,..., argn } )
ArgumentDescription
pipelineobjectThe name of a pipeline user object that contains the pipeline object to be executed
sourcetransThe name of a transaction object with which to connect to the source database
destinationtransThe name of a transaction object with which to connect to the target database
errorobjectThe name of a DataWindow control or Data Store in which to store the pipeline error DataWindow
argn
(optional)One or more retrieval arguments as specified for the pipeline object in the Data Pipeline painter
Return value
Integer. Returns 1 if it succeeds and a negative number if an error occurs. Error values are:
-1 Pipe open failed
-2 Too many columns
-3 Table already exists
-4 Table does not exist
-5 Missing connection
-6 Wrong arguments
-7 Column mismatch
-8 Fatal SQL error in source
-9 Fatal SQL error in destination
-10 Maximum number of errors exceeded
-12 Bad table syntax
-13 Key required but not supplied
-15 Pipe already in progress
-16 Error in source database
-17 Error in destination database
-18 Destination database is read-only
If any argument's value is NULL, Start returns NULL.
Usage
A pipeline transfer involves several PowerBuilder objects. You need:
?A pipeline object, which you define in the Data Pipeline painter. It contains the SQL statements that specify what data is transferred and how that data is mapped from the tables in the source database to those in the target database.
?A user object inherited from the pipeline system object. It inherits properties that let you check the progress of the pipeline transfer. In the painter, you define instance variables and write scripts for pipeline events.
?A window that contains a DataWindow control or a Data Store for the pipeline-error DataWindow. Do not put a DataWindow object in the DataWindow control. The control will display PowerBuilder's pipeline-error DataWindow object if errors occur when the pipeline executes.
The window can also include buttons, menus, or some other means to execute the pipeline, repair errors, and cancel the execution. The scripts for these actions will use the functions Start, Repair, and Cancel.
Before the application executes the pipeline, it needs to connect to the source and destination databases, create an instance of the user object, and assign the pipeline object to the user object's DataObject property. Then it can call Start to execute the pipeline. This code may be in one or several scripts.
When you execute the pipeline, the piped data is committed according to the settings you make in the Data Pipeline painter. You can specify that:
?The data is committed when the pipeline finishes. If the maximum error limit is exceeded, all data is rolled back.
?Data is committed at regular intervals, after a specified number of rows have been transferred. When the maximum error limit is exceeded, all rows already transferred are committed.
For information about specifying the pipeline object in the Data Pipeline painter and how the settings affect committing, see the PowerBuilder User's Guide. For more information on using a pipeline in an application, see Application Techniques.
When you dynamically assign the pipeline object to the user object's DataObject property, you must remember to include the pipeline object in a dynamic library when you build your application's executable.
