![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have to re-work several existing scripts in a medium sized database. My issue is that I would need to change numerous Perform Find script steps to Constrain Found Set script steps. Example of what is there: Set Error Capture [On] Show All Records Perform Find What I would like to have: Set Error Capture [On] Set Field [Table1: ate ; Table2::StartDate & "..." & Table2::EndDateConstrain Found Set This way, users can enter the start & stop dates of the report. Problem, FMPA won't let me copy the Action/Criteria from within the Perform Find. Do I really have to re-enter all of the actions into the Constrain by hand? Man, you'd think there would be a way to change/copy the Perform Find into a Constrain Found Set. Am I missing something simple? Please someone tell me there is a quick easy way to do this. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Reality is the leading cause of stress... ...amongst those in touch with it. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- WinXP Pro 64Bit / FMP Adv 8.5v1 VoicesInMyHead a.k.a. The Voices No, we're not... Yes, we are... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- |
#3
| |||
| |||
|
|
Sorry, I don't know of any. But your post got me thinking that Perform Find may not be necessay. I think I'll start using just Constrain/Extend in my next project and see how it goes. G VoicesInMyHead wrote: I have to re-work several existing scripts in a medium sized database. My issue is that I would need to change numerous Perform Find script steps to Constrain Found Set script steps. Example of what is there: Set Error Capture [On] Show All Records Perform Find What I would like to have: Set Error Capture [On] Set Field [Table1: ate ; Table2::StartDate & "..." & Table2::EndDateConstrain Found Set This way, users can enter the start & stop dates of the report. Problem, FMPA won't let me copy the Action/Criteria from within the Perform Find. Do I really have to re-enter all of the actions into the Constrain by hand? Man, you'd think there would be a way to change/copy the Perform Find into a Constrain Found Set. Am I missing something simple? Please someone tell me there is a quick easy way to do this. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Reality is the leading cause of stress... ...amongst those in touch with it. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- WinXP Pro 64Bit / FMP Adv 8.5v1 VoicesInMyHead a.k.a. The Voices No, we're not... Yes, we are... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- |
#4
| |||
| |||
|
|
Yup. If I am going to Constrain, that's all I use. The example I used was not a real script, I just typed it out... what it should be more like is: Set Error Capture [On] Enter Find Mode #Blank Set Field [Table1: ate ; Table2::StartDate & "..." & Table2::EndDatePerform Find #Blank - but finds date range Constrain Found Set #What I want to find in the date range If you don't have a range to find first, it could just be: Set Error Capture [On] Show All Records Constrain Found Set I just reallllllllly don't want to have to change all the report scripts that were written without the date range ability - days worth of changes. The Voices Grip wrote: Sorry, I don't know of any. But your post got me thinking that Perform Find may not be necessay. I think I'll start using just Constrain/Extend in my next project and see how it goes. G VoicesInMyHead wrote: I have to re-work several existing scripts in a medium sized database. My issue is that I would need to change numerous Perform Find script steps to Constrain Found Set script steps. Example of what is there: Set Error Capture [On] Show All Records Perform Find What I would like to have: Set Error Capture [On] Set Field [Table1: ate ; Table2::StartDate & "..." & Table2::EndDateConstrain Found Set This way, users can enter the start & stop dates of the report. Problem, FMPA won't let me copy the Action/Criteria from within the Perform Find. Do I really have to re-enter all of the actions into the Constrain by hand? Man, you'd think there would be a way to change/copy the Perform Find into a Constrain Found Set. Am I missing something simple? Please someone tell me there is a quick easy way to do this. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Reality is the leading cause of stress... ...amongst those in touch with it. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- WinXP Pro 64Bit / FMP Adv 8.5v1 VoicesInMyHead a.k.a. The Voices No, we're not... Yes, we are... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- |
#5
| |||
| |||
|
|
Yup. If I am going to Constrain, that's all I use. The example I used was not a real script, I just typed it out... what it should be more like is: Set Error Capture [On] Enter Find Mode #Blank Set Field [Table1: ate ; Table2::StartDate & "..." & Table2::EndDatePerform Find #Blank - but finds date range Constrain Found Set #What I want to find in the date range If you don't have a range to find first, it could just be: Set Error Capture [On] Show All Records Constrain Found Set I just reallllllllly don't want to have to change all the report scripts that were written without the date range ability - days worth of changes. The Voices Grip wrote: Sorry, I don't know of any. But your post got me thinking that Perform Find may not be necessay. I think I'll start using just Constrain/Extend in my next project and see how it goes. G VoicesInMyHead wrote: I have to re-work several existing scripts in a medium sized database. My issue is that I would need to change numerous Perform Find script steps to Constrain Found Set script steps. Example of what is there: Set Error Capture [On] Show All Records Perform Find What I would like to have: Set Error Capture [On] Set Field [Table1: ate ; Table2::StartDate & "..." & Table2::EndDateConstrain Found Set This way, users can enter the start & stop dates of the report. Problem, FMPA won't let me copy the Action/Criteria from within the Perform Find. Do I really have to re-enter all of the actions into the Constrain by hand? Man, you'd think there would be a way to change/copy the Perform Find into a Constrain Found Set. Am I missing something simple? Please someone tell me there is a quick easy way to do this. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Reality is the leading cause of stress... ...amongst those in touch with it. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- WinXP Pro 64Bit / FMP Adv 8.5v1 VoicesInMyHead a.k.a. The Voices No, we're not... Yes, we are... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- |
#6
| ||||
| ||||
|
|
Actually there is two mistakes in your find criterion. |
|
One : you can't use 'Set Field( date; Something)' if that 'Something is not a date ie MM/DD/YYYY.... |
|
Two : StartDate and EndDate have to be set as globals... |
|
After having corrected these, you will not need any longer to 'Constrain' the Found Set. |
#7
| |||
| |||
|
|
I all the script steps are allways the same, create a completely new script with these steps. Call it [SS] ContrainIT (or whatever) and treat it as a SubScript. Then in all the scripts where you need it just replace the current steps you have with one step: Perform Script <[SS] ConstrainIT Ursus "VoicesInMyHead" <voices.imh (AT) gmail (DOT) com> schreef in bericht news:1169497868.920510.88450 (AT) l53g2000cwa (DOT) googlegroups.com... Yup. If I am going to Constrain, that's all I use. The example I used was not a real script, I just typed it out... what it should be more like is: Set Error Capture [On] Enter Find Mode #Blank Set Field [Table1: ate ; Table2::StartDate & "..." & Table2::EndDatePerform Find #Blank - but finds date range Constrain Found Set #What I want to find in the date range If you don't have a range to find first, it could just be: Set Error Capture [On] Show All Records Constrain Found Set I just reallllllllly don't want to have to change all the report scripts that were written without the date range ability - days worth of changes. The Voices Grip wrote: Sorry, I don't know of any. But your post got me thinking that Perform Find may not be necessay. I think I'll start using just Constrain/Extend in my next project and see how it goes. G VoicesInMyHead wrote: I have to re-work several existing scripts in a medium sized database. My issue is that I would need to change numerous Perform Find script steps to Constrain Found Set script steps. Example of what is there: Set Error Capture [On] Show All Records Perform Find What I would like to have: Set Error Capture [On] Set Field [Table1: ate ; Table2::StartDate & "..." & Table2::EndDateConstrain Found Set This way, users can enter the start & stop dates of the report. Problem, FMPA won't let me copy the Action/Criteria from within the Perform Find. Do I really have to re-enter all of the actions into the Constrain by hand? Man, you'd think there would be a way to change/copy the Perform Find into a Constrain Found Set. Am I missing something simple? Please someone tell me there is a quick easy way to do this. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Reality is the leading cause of stress... ...amongst those in touch with it. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- WinXP Pro 64Bit / FMP Adv 8.5v1 VoicesInMyHead a.k.a. The Voices No, we're not... Yes, we are... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- |
#8
| |||
| |||
|
|
Actually there is two mistakes in your find criterion. No. There are not. One : you can't use 'Set Field( date; Something)' if that 'Something is not a date ie MM/DD/YYYY.... My fields are dates, and they work just fine. Two : StartDate and EndDate have to be set as globals... They are. Again, works fine - always has. If you read my post, it said nothing about anything "not" working. I am simply updating old search scripts to conform to their growing data needs. After having corrected these, you will not need any longer to 'Constrain' the Found Set. There is nothing to correct... and yes: if you are doing a sub-search, you need to Constrain or Extend your set - if you just do another Perform Find, FMP looks at ALL records, not the found set (date range in my example) you are working with. Thanks anyway? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Reality is the leading cause of stress... ...amongst those in touch with it. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- WinXP Pro 64Bit / FMP Adv 8.5v1 VoicesInMyHead a.k.a. The Voices No, we're not... Yes, we are... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- |
#9
| |||
| |||
|
|
OK, if you say so : I take it for granted. Maybe it was true only for FMP6. Sorry to have somewhat disturbed you with apparently inappropriate comments. Except for the word 'mistake' that you said was not true, I tested what I said in FM8, so what I proposed works (also). And I didn't understand that you wanted to do another find after the first find, which then calls for a 'Constrain' or 'Extend' search. Fortunately, Ursus gave you a better answer to the question you asked. Remi-Noel "VoicesInMyHead" <voices.... (AT) gmail (DOT) com> a écrit dans le message de news: 1169559384.899337.177... (AT) v45g2000cwv (DOT) googlegroups.com... Actually there is two mistakes in your find criterion. No. There are not. One : you can't use 'Set Field( date; Something)' if that 'Something is not a date ie MM/DD/YYYY.... My fields are dates, and they work just fine. Two : StartDate and EndDate have to be set as globals... They are. Again, works fine - always has. If you read my post, it said nothing about anything "not" working. I am simply updating old search scripts to conform to their growing data needs. After having corrected these, you will not need any longer to 'Constrain' the Found Set. There is nothing to correct... and yes: if you are doing a sub-search, you need to Constrain or Extend your set - if you just do another Perform Find, FMP looks at ALL records, not the found set (date range in my example) you are working with. Thanks anyway? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Reality is the leading cause of stress... ...amongst those in touch with it. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- WinXP Pro 64Bit / FMP Adv 8.5v1 VoicesInMyHead a.k.a. The Voices No, we're not... Yes, we are... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- |
#10
| |||
| |||
|
|
At best; these guys like Remi and Ursus can only "guess' at what you are doing exactly. For the most part they do a great job. It's hard to know exactly what your design looks like a couple of thousand miles away. I would try a little more etiquette in response to these guys when they can't see into a crystal ball. Their expertise is invaluable. JC- Hide quoted text -- Show quoted text - |
![]() |
| Thread Tools | |
| Display Modes | |
| |