كيف نخرج تقرير بشكل دورى كل فتره زمنيه بدون استدعائه من خلال زر
ويحفظ فى مجلد مخصص لذلك ولكن فى صيغة ملف ورد

عليك ان تتعرف على ال
dbms_job
وضيفة هذه الباكج تنفيذ عمل معين حسب الفترة التي تحددها لها
يجب عليك ان تعرف كيف تشغل التقرير من الداتا بيز واليك يا سيدي التالي

11.3 Invoking a Report From a Database Event
Database triggers are the primary mechanism for invoking reports using the
Event-Driven Publishing API. The Oracle database allows you to define various
scopes of triggers that fire in response to various events. To submit a
database-driven job, you use the code described in the previous sections within a
database trigger.
There are many ways to use event-driven publishing. One way is to create security
protocols using a trigger that fires whenever a grant is done or a user logs on or off.
Another way is to create automated processes that respond to certain types of
changes to data in a table. For example, a database trigger could fire when the
status of an expense report changes to DONE; in turn, a report could automatically
be sent to an employee's manager.
For example:
CREATE TRIGGER EXP_REP_TRG
AFTER INSERT OR UPDATE on EXP_REP FOR EACH ROW
myPlist SRW_PARAMLIST;
myIdent SRW.Job_Ident;
BEGIN
IF (:new.ExpStat = 'DONE') THEN
myPlist := SRW_PARAMLIST(SRW_PARAMETER('',''));
srw.add_parameter(myPlist,'GATEWAY','http://…');
srw.add_parameter(myPlist,'SERVER','fooSVR');
srw.add_parameter(myPlist,'REPORT','foo.RDF');
srw.add_parameter(myPlist,'USERID','foo/bar');
srw.add_parameter(myPlist,'ExpenseID',:new.ExpID);
myIdent := srw.run_report(myPlist);
END IF;
END;
This trigger will fire after each update on the EXP_REP table. In the event the status
changes to DONE, the report request is run.
If you want your request to run against a key specified in the cgicmd.dat file,
specify the CMDKEY parameter in lieu of the REPORT parameter. If the key contains
user ID information, you can omit the USERID parameter as well. For example:
CREATE TRIGGER EXP_REP_TRG
AFTER INSERT OR UPDATE on EXP_REP FOR EACH ROW
myPlist SRW_PARAMLIST;
myIdent SRW.Job_Ident;
BEGIN
IF (:new.ExpStat = 'DONE') THEN
Integrating with Oracle9i Advanced Queuing
Event-Driven Publishing 11-9
myPlist := SRW_PARAMLIST(SRW_PARAMETER('',''));
srw.add_parameter(myPlist,'GATEWAY','http://…');
srw.add_parameter(myPlist,'SERVER','fooSVR');
srw.add_parameter(myPlist,'CMDKEY','keyvalue');
srw.add_parameter(myPlist,'ExpenseID',:new.ExpID);
myIdent := srw.run_report(myPlist);
END IF;
END;
Additionally, if you have defined an advanced distribution model via a distribution
XML file, you can specify that file with the DIST parameter. For example:
CREATE TRIGGER EXP_REP_TRG
AFTER INSERT OR UPDATE on EXP_REP FOR EACH ROW
myPlist SRW_PARAMLIST;
myIdent SRW.Job_Ident;
BEGIN
IF (:new.ExpStat = 'DONE') THEN
myPlist := SRW_PARAMLIST(SRW_PARAMETER('',''));
srw.add_parameter(myPlist,'GATEWAY','http://…');
srw.add_parameter(myPlist,'SERVER','fooSVR');
srw.add_parameter(myPlist,'REPORT','foo.RDF');
srw.add_parameter(myPlist,'USERID','foo/bar');
srw.add_parameter(myPlist,'DISTRIBUTE','YES');
srw.add_parameter(myPlist,'DESTINATION','filename.xml');
srw.add_parameter(myPlist,'ExpenseID',:new.ExpID);
myIdent := srw.run_report(myPlist);
END IF;
END;
This is one way to move this kind of logic from your application into the database
and use the database as a central storage for business processes.

طريقك طويل بس رح تستفيد والله على ما اقول شهيد

اما يا باشا التقارير الان اما ان تكون بصيغه html pdf rtf
طيب شو رايك ناخذ صيغة rtf ولما تعمل داونلود على الكلينت حولها الى doc

ولا تنسانا بدعاء صالح والى الامام جميعاً

الف شكر اخ مصطفى وربنا يوفقق
والى الامام دئما