PDA

View Full Version : Sample Example Of Using DDO's in BPO WORKSPACE



Peter A Donovan
10-Nov-2006, 07:24 AM
Entire Workspace: C:\BPOExample

Inspired by Jorgen. Free on www.SonataSoftware.US
See the VDF Instruction menu for:

Actual Real Life BPO Using DDO's To Process Example Workspace (Click To
Download Zip)

(It's 4.8 MB and too large to post)

It actually contains no data so the proof of the pudding is for Jorgen to
fill in the data and process it and report back. The techniques in it are
worth the look including the STATLOG Monitor and utility included.
--
Regards,
Peter
Sonata Software: www.SonataSoftware.US
Northeast DataFlex Consortium Member: www.NEDataFlex.Com

Peter A Donovan
21-Nov-2006, 06:53 PM
Change Of Website (Same Download Available)

www.ApplauseSoftware.Com

--
Regards,
Peter
Applause Software, http://www.ApplauseSoftware.Com
Northeast DataFlex Consortium Member: www.NEDataFlex.Com
"Peter A Donovan" <SonataSoftwareUS@Yahoo.Com> wrote in message
news:mPyz$MMBHHA.3924@dacmail.dataaccess.com...
> Entire Workspace: C:\BPOExample
>
> Inspired by Jorgen. Free on www.SonataSoftware.US
> See the VDF Instruction menu for:
>
> Actual Real Life BPO Using DDO's To Process Example Workspace (Click To
> Download Zip)
>
> (It's 4.8 MB and too large to post)
>
> It actually contains no data so the proof of the pudding is for Jorgen to
> fill in the data and process it and report back. The techniques in it are
> worth the look including the STATLOG Monitor and utility included.
> --
> Regards,
> Peter
> Sonata Software: www.SonataSoftware.US
> Northeast DataFlex Consortium Member: www.NEDataFlex.Com
>

Jørgen Münster
29-Nov-2006, 12:29 PM
Hi Peter

Now I have done some intensive testing of the BPO and only found a few
mistakes ;-)

The following line (no 206 in the BPO) prevents the creation of the first
invoice. I simply removed it:

If (iLastCustomerID = 0) Move Subscr.Customer_id to iLastCustomerID

The following line (no 208 in the BPO) clears all parents so the first
invoice line fails for all customers:

Send Clear of Invhead_DD

I repaired it by adding an additional Find right after, but maybe the logic
needs to be changed to serve as a good example:

Send Find of Subscr_DD eq 4 //Note: find EQ

Still, I am getting an error 999 Invalid Value that closes the BPO. If I
remove the Begin/End_Transaction I actually get all my invoices as expected
but in addition I get an error 999 for each subscription. I think the
problem is connected to the field postalcode in Customer and Zip, but I
can't solve it.

However, this example show two things: It is very easy to make a mistake in
a BPO using DataDictionaries, and you get no feedback. If you check for
errors after every Send Request, all that is returned from the DD's is an
Error 1. It's quite difficult to know what went wrong and how to debug it.

A few more comments of the topic: In the real world I would move the
Invoiced field from Service to Subscr and the Constrain should move as well.
After selecting the Workspace the Studio Database must be reindexed (the
local df_collate might differ from yours). Finally, you should consider
using the ToOEM Function in your StatLog utility as the user's name can hold
national characters.

Having a working DD-sample available when I started using VDF 6 years ago
would have been of great value for me.

Thank you for the BPO code. I hope you will modify it, so we all can benefit
from it in the future.

Sincerely
Jørgen


"Peter A Donovan" <SonataSoftwareUS@Yahoo.Com> skrev i en meddelelse
news:mPyz$MMBHHA.3924@dacmail.dataaccess.com...
> Entire Workspace: C:\BPOExample
>
> Inspired by Jorgen. Free on www.SonataSoftware.US
> See the VDF Instruction menu for:
>
> Actual Real Life BPO Using DDO's To Process Example Workspace (Click To
> Download Zip)
>
> (It's 4.8 MB and too large to post)
>
> It actually contains no data so the proof of the pudding is for Jorgen to
> fill in the data and process it and report back. The techniques in it are
> worth the look including the STATLOG Monitor and utility included.
> --
> Regards,
> Peter
> Sonata Software: www.SonataSoftware.US
> Northeast DataFlex Consortium Member: www.NEDataFlex.Com
>

Peter A Donovan
29-Nov-2006, 01:46 PM
Hi Jorgen,
Thanks for taking the time to test: I guess that "If it compiles it must be
ok" doesn't always hold true!

The transaction block essentially makes it so that each and every aspect of
the invoice has been validated ok and the invoice is 100% validated. No
invoice if any part of the invoice doesn't validate. Rerun after fixing
writes the invoice.

The enclosed BPO STATLOG utility should show
1. The Error
2. The DDO That offered the error
3. The Line number that the errror occured on.

I will take another shot at this with some data when I get a chance, and I
thank you for your other comments.

PS: Due to my website management, the file workspace referenced above no
longer exists, but I will put it up on an FTP as soon as I am able to for
others to see.

Regards,
Peter
Applause Software,
www.ApplauseSoftware.Com
Northeast DataFlex Consortium Member: www.NEDataFlex.Com

"Jørgen Münster" <jfm@it.dk> wrote in message
news:pAyKCw9EHHA.3804@dacmail.dataaccess.com...
> Hi Peter
>
> Now I have done some intensive testing of the BPO and only found a few
> mistakes ;-)
>
> The following line (no 206 in the BPO) prevents the creation of the first
> invoice. I simply removed it:
>
> If (iLastCustomerID = 0) Move Subscr.Customer_id to iLastCustomerID
>
> The following line (no 208 in the BPO) clears all parents so the first
> invoice line fails for all customers:
>
> Send Clear of Invhead_DD
>
> I repaired it by adding an additional Find right after, but maybe the
> logic needs to be changed to serve as a good example:
>
> Send Find of Subscr_DD eq 4 //Note: find EQ
>
> Still, I am getting an error 999 Invalid Value that closes the BPO. If I
> remove the Begin/End_Transaction I actually get all my invoices as
> expected but in addition I get an error 999 for each subscription. I think
> the problem is connected to the field postalcode in Customer and Zip, but
> I can't solve it.
>
> However, this example show two things: It is very easy to make a mistake
> in a BPO using DataDictionaries, and you get no feedback. If you check for
> errors after every Send Request, all that is returned from the DD's is an
> Error 1. It's quite difficult to know what went wrong and how to debug it.
>
> A few more comments of the topic: In the real world I would move the
> Invoiced field from Service to Subscr and the Constrain should move as
> well. After selecting the Workspace the Studio Database must be reindexed
> (the local df_collate might differ from yours). Finally, you should
> consider using the ToOEM Function in your StatLog utility as the user's
> name can hold national characters.
>
> Having a working DD-sample available when I started using VDF 6 years ago
> would have been of great value for me.
>
> Thank you for the BPO code. I hope you will modify it, so we all can
> benefit from it in the future.
>
> Sincerely
> Jørgen
>
>
> "Peter A Donovan" <SonataSoftwareUS@Yahoo.Com> skrev i en meddelelse
> news:mPyz$MMBHHA.3924@dacmail.dataaccess.com...
>> Entire Workspace: C:\BPOExample
>>
>> Inspired by Jorgen. Free on www.SonataSoftware.US
>> See the VDF Instruction menu for:
>>
>> Actual Real Life BPO Using DDO's To Process Example Workspace (Click To
>> Download Zip)
>>
>> (It's 4.8 MB and too large to post)
>>
>> It actually contains no data so the proof of the pudding is for Jorgen to
>> fill in the data and process it and report back. The techniques in it
>> are worth the look including the STATLOG Monitor and utility included.
>> --
>> Regards,
>> Peter
>> Sonata Software: www.SonataSoftware.US
>> Northeast DataFlex Consortium Member: www.NEDataFlex.Com
>>
>
>

Jørgen Münster
30-Nov-2006, 03:50 AM
Hi Peter

I have attached a screen shot of the Statlog. Maybe it will help you (I see
no line numbers).

Regards
Jørgen


"Peter A Donovan" <SonataSoftwareUS@Yahoo.Com> skrev i en meddelelse
news:qK$gJb%23EHHA.3804@dacmail.dataaccess.com...
> Hi Jorgen,
> Thanks for taking the time to test: I guess that "If it compiles it must
> be
> ok" doesn't always hold true!
>
> The transaction block essentially makes it so that each and every aspect
> of
> the invoice has been validated ok and the invoice is 100% validated. No
> invoice if any part of the invoice doesn't validate. Rerun after fixing
> writes the invoice.
>
> The enclosed BPO STATLOG utility should show
> 1. The Error
> 2. The DDO That offered the error
> 3. The Line number that the errror occured on.
>
> I will take another shot at this with some data when I get a chance, and I
> thank you for your other comments.
>
> PS: Due to my website management, the file workspace referenced above no
> longer exists, but I will put it up on an FTP as soon as I am able to for
> others to see.
>
> Regards,
> Peter
> Applause Software,
> www.ApplauseSoftware.Com
> Northeast DataFlex Consortium Member: www.NEDataFlex.Com
>
> "Jørgen Münster" <jfm@it.dk> wrote in message
> news:pAyKCw9EHHA.3804@dacmail.dataaccess.com...
>> Hi Peter
>>
>> Now I have done some intensive testing of the BPO and only found a few
>> mistakes ;-)
>>
>> The following line (no 206 in the BPO) prevents the creation of the first
>> invoice. I simply removed it:
>>
>> If (iLastCustomerID = 0) Move Subscr.Customer_id to iLastCustomerID
>>
>> The following line (no 208 in the BPO) clears all parents so the first
>> invoice line fails for all customers:
>>
>> Send Clear of Invhead_DD
>>
>> I repaired it by adding an additional Find right after, but maybe the
>> logic needs to be changed to serve as a good example:
>>
>> Send Find of Subscr_DD eq 4 //Note: find EQ
>>
>> Still, I am getting an error 999 Invalid Value that closes the BPO. If I
>> remove the Begin/End_Transaction I actually get all my invoices as
>> expected but in addition I get an error 999 for each subscription. I
>> think
>> the problem is connected to the field postalcode in Customer and Zip, but
>> I can't solve it.
>>
>> However, this example show two things: It is very easy to make a mistake
>> in a BPO using DataDictionaries, and you get no feedback. If you check
>> for
>> errors after every Send Request, all that is returned from the DD's is an
>> Error 1. It's quite difficult to know what went wrong and how to debug
>> it.
>>
>> A few more comments of the topic: In the real world I would move the
>> Invoiced field from Service to Subscr and the Constrain should move as
>> well. After selecting the Workspace the Studio Database must be reindexed
>> (the local df_collate might differ from yours). Finally, you should
>> consider using the ToOEM Function in your StatLog utility as the user's
>> name can hold national characters.
>>
>> Having a working DD-sample available when I started using VDF 6 years ago
>> would have been of great value for me.
>>
>> Thank you for the BPO code. I hope you will modify it, so we all can
>> benefit from it in the future.
>>
>> Sincerely
>> Jørgen
>>
>>
>> "Peter A Donovan" <SonataSoftwareUS@Yahoo.Com> skrev i en meddelelse
>> news:mPyz$MMBHHA.3924@dacmail.dataaccess.com...
>>> Entire Workspace: C:\BPOExample
>>>
>>> Inspired by Jorgen. Free on www.SonataSoftware.US
>>> See the VDF Instruction menu for:
>>>
>>> Actual Real Life BPO Using DDO's To Process Example Workspace (Click
>>> To
>>> Download Zip)
>>>
>>> (It's 4.8 MB and too large to post)
>>>
>>> It actually contains no data so the proof of the pudding is for Jorgen
>>> to
>>> fill in the data and process it and report back. The techniques in it
>>> are worth the look including the STATLOG Monitor and utility included.
>>> --
>>> Regards,
>>> Peter
>>> Sonata Software: www.SonataSoftware.US
>>> Northeast DataFlex Consortium Member: www.NEDataFlex.Com
>>>
>>
>>
>
>

LasseJ
18-Mar-2007, 04:52 PM
Hi Peter,

Where can I find this workspace to download? I, like obviously a lot of
others, have a problem to make the DDO approach work in BPO's. Sometimes it
works, sometimes it doesn't, and I can't figure out why. :-)
I would realy like to study this workspace.

/Lars J
"Peter A Donovan" <SonataSoftwareUS@Yahoo.Com> skrev i meddelandet
news:qK$gJb%23EHHA.3804@dacmail.dataaccess.com...
> Hi Jorgen,
> Thanks for taking the time to test: I guess that "If it compiles it must
be
> ok" doesn't always hold true!
>
> The transaction block essentially makes it so that each and every aspect
of
> the invoice has been validated ok and the invoice is 100% validated. No
> invoice if any part of the invoice doesn't validate. Rerun after fixing
> writes the invoice.
>
> The enclosed BPO STATLOG utility should show
> 1. The Error
> 2. The DDO That offered the error
> 3. The Line number that the errror occured on.
>
> I will take another shot at this with some data when I get a chance, and I
> thank you for your other comments.
>
> PS: Due to my website management, the file workspace referenced above no
> longer exists, but I will put it up on an FTP as soon as I am able to for
> others to see.
>
> Regards,
> Peter
> Applause Software,
> www.ApplauseSoftware.Com
> Northeast DataFlex Consortium Member: www.NEDataFlex.Com
>
> "Jørgen Münster" <jfm@it.dk> wrote in message
> news:pAyKCw9EHHA.3804@dacmail.dataaccess.com...
> > Hi Peter
> >
> > Now I have done some intensive testing of the BPO and only found a few
> > mistakes ;-)
> >
> > The following line (no 206 in the BPO) prevents the creation of the
first
> > invoice. I simply removed it:
> >
> > If (iLastCustomerID = 0) Move Subscr.Customer_id to iLastCustomerID
> >
> > The following line (no 208 in the BPO) clears all parents so the first
> > invoice line fails for all customers:
> >
> > Send Clear of Invhead_DD
> >
> > I repaired it by adding an additional Find right after, but maybe the
> > logic needs to be changed to serve as a good example:
> >
> > Send Find of Subscr_DD eq 4 //Note: find EQ
> >
> > Still, I am getting an error 999 Invalid Value that closes the BPO. If I
> > remove the Begin/End_Transaction I actually get all my invoices as
> > expected but in addition I get an error 999 for each subscription. I
think
> > the problem is connected to the field postalcode in Customer and Zip,
but
> > I can't solve it.
> >
> > However, this example show two things: It is very easy to make a mistake
> > in a BPO using DataDictionaries, and you get no feedback. If you check
for
> > errors after every Send Request, all that is returned from the DD's is
an
> > Error 1. It's quite difficult to know what went wrong and how to debug
it.
> >
> > A few more comments of the topic: In the real world I would move the
> > Invoiced field from Service to Subscr and the Constrain should move as
> > well. After selecting the Workspace the Studio Database must be
reindexed
> > (the local df_collate might differ from yours). Finally, you should
> > consider using the ToOEM Function in your StatLog utility as the user's
> > name can hold national characters.
> >
> > Having a working DD-sample available when I started using VDF 6 years
ago
> > would have been of great value for me.
> >
> > Thank you for the BPO code. I hope you will modify it, so we all can
> > benefit from it in the future.
> >
> > Sincerely
> > Jørgen
> >
> >
> > "Peter A Donovan" <SonataSoftwareUS@Yahoo.Com> skrev i en meddelelse
> > news:mPyz$MMBHHA.3924@dacmail.dataaccess.com...
> >> Entire Workspace: C:\BPOExample
> >>
> >> Inspired by Jorgen. Free on www.SonataSoftware.US
> >> See the VDF Instruction menu for:
> >>
> >> Actual Real Life BPO Using DDO's To Process Example Workspace (Click
To
> >> Download Zip)
> >>
> >> (It's 4.8 MB and too large to post)
> >>
> >> It actually contains no data so the proof of the pudding is for Jorgen
to
> >> fill in the data and process it and report back. The techniques in it
> >> are worth the look including the STATLOG Monitor and utility included.
> >> --
> >> Regards,
> >> Peter
> >> Sonata Software: www.SonataSoftware.US
> >> Northeast DataFlex Consortium Member: www.NEDataFlex.Com
> >>
> >
> >
>
>

ApplauseBoston
19-Mar-2007, 04:36 PM
Hi Lars,
Sorry, but due to a lost trademark dispute, SonataSoftware.US is no longer
owned or operated by me: it is owned now by Sonata Software LTD of India.

Don't ask!

Note: many of the difficulties with DDO Trees in BPO's had to due with the
fact that the parent ddo's respected their settings as a parent and made
most of the columns noenter.
In my experience, VDF12 has removed the "set Main_DDO" to...... which causes
the BPO to be quite more friendly and allow saving values to the parents.

For an example of DDO processing in a bpo the best I can offer is RoloFlex
which has such. Suggest you re-try with VDF12 and/or check RoloFlex for
code attached to the download. Free CRM from my website.
--
Regards,
Peter
Applause Software, http://www.ApplauseSoftware.Com
Northeast DataFlex Consortium Member: www.NEDataFlex.Com


"Lars Jarnhäll" <LasseJ@oasystem.se> wrote in message
news:S6oRdfaaHHA.5880@dacmail.dataaccess.com...
> Hi Peter,
>
> Where can I find this workspace to download? I, like obviously a lot of
> others, have a problem to make the DDO approach work in BPO's. Sometimes
> it
> works, sometimes it doesn't, and I can't figure out why. :-)
> I would realy like to study this workspace.
>
> /Lars J
> "Peter A Donovan" <SonataSoftwareUS@Yahoo.Com> skrev i meddelandet
> news:qK$gJb%23EHHA.3804@dacmail.dataaccess.com...
>> Hi Jorgen,
>> Thanks for taking the time to test: I guess that "If it compiles it must
> be
>> ok" doesn't always hold true!
>>
>> The transaction block essentially makes it so that each and every aspect
> of
>> the invoice has been validated ok and the invoice is 100% validated. No
>> invoice if any part of the invoice doesn't validate. Rerun after fixing
>> writes the invoice.
>>
>> The enclosed BPO STATLOG utility should show
>> 1. The Error
>> 2. The DDO That offered the error
>> 3. The Line number that the errror occured on.
>>
>> I will take another shot at this with some data when I get a chance, and
>> I
>> thank you for your other comments.
>>
>> PS: Due to my website management, the file workspace referenced above no
>> longer exists, but I will put it up on an FTP as soon as I am able to for
>> others to see.
>>
>> Regards,
>> Peter
>> Applause Software,
>> www.ApplauseSoftware.Com
>> Northeast DataFlex Consortium Member: www.NEDataFlex.Com
>>
>> "Jørgen Münster" <jfm@it.dk> wrote in message
>> news:pAyKCw9EHHA.3804@dacmail.dataaccess.com...
>> > Hi Peter
>> >
>> > Now I have done some intensive testing of the BPO and only found a few
>> > mistakes ;-)
>> >
>> > The following line (no 206 in the BPO) prevents the creation of the
> first
>> > invoice. I simply removed it:
>> >
>> > If (iLastCustomerID = 0) Move Subscr.Customer_id to iLastCustomerID
>> >
>> > The following line (no 208 in the BPO) clears all parents so the first
>> > invoice line fails for all customers:
>> >
>> > Send Clear of Invhead_DD
>> >
>> > I repaired it by adding an additional Find right after, but maybe the
>> > logic needs to be changed to serve as a good example:
>> >
>> > Send Find of Subscr_DD eq 4 //Note: find EQ
>> >
>> > Still, I am getting an error 999 Invalid Value that closes the BPO. If
>> > I
>> > remove the Begin/End_Transaction I actually get all my invoices as
>> > expected but in addition I get an error 999 for each subscription. I
> think
>> > the problem is connected to the field postalcode in Customer and Zip,
> but
>> > I can't solve it.
>> >
>> > However, this example show two things: It is very easy to make a
>> > mistake
>> > in a BPO using DataDictionaries, and you get no feedback. If you check
> for
>> > errors after every Send Request, all that is returned from the DD's is
> an
>> > Error 1. It's quite difficult to know what went wrong and how to debug
> it.
>> >
>> > A few more comments of the topic: In the real world I would move the
>> > Invoiced field from Service to Subscr and the Constrain should move as
>> > well. After selecting the Workspace the Studio Database must be
> reindexed
>> > (the local df_collate might differ from yours). Finally, you should
>> > consider using the ToOEM Function in your StatLog utility as the user's
>> > name can hold national characters.
>> >
>> > Having a working DD-sample available when I started using VDF 6 years
> ago
>> > would have been of great value for me.
>> >
>> > Thank you for the BPO code. I hope you will modify it, so we all can
>> > benefit from it in the future.
>> >
>> > Sincerely
>> > Jørgen
>> >
>> >
>> > "Peter A Donovan" <SonataSoftwareUS@Yahoo.Com> skrev i en meddelelse
>> > news:mPyz$MMBHHA.3924@dacmail.dataaccess.com...
>> >> Entire Workspace: C:\BPOExample
>> >>
>> >> Inspired by Jorgen. Free on www.SonataSoftware.US
>> >> See the VDF Instruction menu for:
>> >>
>> >> Actual Real Life BPO Using DDO's To Process Example Workspace (Click
> To
>> >> Download Zip)
>> >>
>> >> (It's 4.8 MB and too large to post)
>> >>
>> >> It actually contains no data so the proof of the pudding is for Jorgen
> to
>> >> fill in the data and process it and report back. The techniques in it
>> >> are worth the look including the STATLOG Monitor and utility included.
>> >> --
>> >> Regards,
>> >> Peter
>> >> Sonata Software: www.SonataSoftware.US
>> >> Northeast DataFlex Consortium Member: www.NEDataFlex.Com
>> >>
>> >
>> >
>>
>>
>
>

Graham Goodwin
20-Apr-2007, 02:39 AM
Peter

Is it still possible to download the file workspace? I cannot find it at all
on your website.

Many thanks. Regards

Graham Goodwin

"Peter A Donovan" <SonataSoftwareUS@Yahoo.Com> wrote in message
news:qK$gJb%23EHHA.3804@dacmail.dataaccess.com...
> Hi Jorgen,
> Thanks for taking the time to test: I guess that "If it compiles it must
> be ok" doesn't always hold true!
>
> The transaction block essentially makes it so that each and every aspect
> of the invoice has been validated ok and the invoice is 100% validated.
> No invoice if any part of the invoice doesn't validate. Rerun after
> fixing writes the invoice.
>
> The enclosed BPO STATLOG utility should show
> 1. The Error
> 2. The DDO That offered the error
> 3. The Line number that the errror occured on.
>
> I will take another shot at this with some data when I get a chance, and I
> thank you for your other comments.
>
> PS: Due to my website management, the file workspace referenced above no
> longer exists, but I will put it up on an FTP as soon as I am able to for
> others to see.
>
> Regards,
> Peter
> Applause Software,
> www.ApplauseSoftware.Com
> Northeast DataFlex Consortium Member: www.NEDataFlex.Com
>
> "Jørgen Münster" <jfm@it.dk> wrote in message
> news:pAyKCw9EHHA.3804@dacmail.dataaccess.com...
>> Hi Peter
>>
>> Now I have done some intensive testing of the BPO and only found a few
>> mistakes ;-)
>>
>> The following line (no 206 in the BPO) prevents the creation of the first
>> invoice. I simply removed it:
>>
>> If (iLastCustomerID = 0) Move Subscr.Customer_id to iLastCustomerID
>>
>> The following line (no 208 in the BPO) clears all parents so the first
>> invoice line fails for all customers:
>>
>> Send Clear of Invhead_DD
>>
>> I repaired it by adding an additional Find right after, but maybe the
>> logic needs to be changed to serve as a good example:
>>
>> Send Find of Subscr_DD eq 4 //Note: find EQ
>>
>> Still, I am getting an error 999 Invalid Value that closes the BPO. If I
>> remove the Begin/End_Transaction I actually get all my invoices as
>> expected but in addition I get an error 999 for each subscription. I
>> think the problem is connected to the field postalcode in Customer and
>> Zip, but I can't solve it.
>>
>> However, this example show two things: It is very easy to make a mistake
>> in a BPO using DataDictionaries, and you get no feedback. If you check
>> for errors after every Send Request, all that is returned from the DD's
>> is an Error 1. It's quite difficult to know what went wrong and how to
>> debug it.
>>
>> A few more comments of the topic: In the real world I would move the
>> Invoiced field from Service to Subscr and the Constrain should move as
>> well. After selecting the Workspace the Studio Database must be reindexed
>> (the local df_collate might differ from yours). Finally, you should
>> consider using the ToOEM Function in your StatLog utility as the user's
>> name can hold national characters.
>>
>> Having a working DD-sample available when I started using VDF 6 years ago
>> would have been of great value for me.
>>
>> Thank you for the BPO code. I hope you will modify it, so we all can
>> benefit from it in the future.
>>
>> Sincerely
>> Jørgen
>>
>>
>> "Peter A Donovan" <SonataSoftwareUS@Yahoo.Com> skrev i en meddelelse
>> news:mPyz$MMBHHA.3924@dacmail.dataaccess.com...
>>> Entire Workspace: C:\BPOExample
>>>
>>> Inspired by Jorgen. Free on www.SonataSoftware.US
>>> See the VDF Instruction menu for:
>>>
>>> Actual Real Life BPO Using DDO's To Process Example Workspace (Click
>>> To Download Zip)
>>>
>>> (It's 4.8 MB and too large to post)
>>>
>>> It actually contains no data so the proof of the pudding is for Jorgen
>>> to fill in the data and process it and report back. The techniques in
>>> it are worth the look including the STATLOG Monitor and utility
>>> included.
>>> --
>>> Regards,
>>> Peter
>>> Sonata Software: www.SonataSoftware.US
>>> Northeast DataFlex Consortium Member: www.NEDataFlex.Com
>>>
>>
>>
>
>