![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
These are common confusions with FM7. Here are your answers. 1. The 'Specify Found Request' dialog box isn't extremely useful, as you can only input a set value. Instead, do the following in your script: Enter Find Mode[] SetField[A, 'data'] PerformFind[] |
|
2. You can check for an empty field with the IsEmpty() function. On the other hand, you can use the 'Set Error Capture' script step 'on' to hide any error message that might pop up if the user does a blank find. |
#4
| |||
| |||
|
| audleman (AT) quasika (DOT) net wrote: These are common confusions with FM7. Here are your answers. 1. The 'Specify Found Request' dialog box isn't extremely useful, as you can only input a set value. Instead, do the following in your script: Enter Find Mode[] SetField[A, 'data'] PerformFind[] Thanks for the answer, but onfortunalety it is not the answer for my my question. But looking your steps maybey you bring me to another thought, I have to try later these days (less time now). What I need is that the 'data' in your "SetField [A, 'data']" step is taken from the contents of a field from a related table. The related table do have only one record with base information for the entire database. The related table is connected with use of the "X" mark ---------X----------- so data is valid for every record in the related second "big" table with many records. The data for the search script has to be looked up in that particular "one" record of the related base information field, and to be used for searching into the second table. |
#5
| |||
| |||
|
|
mail.to.me (AT) fotograaf (DOT) invalid says... audleman (AT) quasika (DOT) net wrote: These are common confusions with FM7. Here are your answers. 1. The 'Specify Found Request' dialog box isn't extremely useful, as you can only input a set value. Instead, do the following in your script: Enter Find Mode[] SetField[A, 'data'] PerformFind[] Thanks for the answer, but onfortunalety it is not the answer for my my question. But looking your steps maybey you bring me to another thought, I have to try later these days (less time now). What I need is that the 'data' in your "SetField [A, 'data']" step is taken from the contents of a field from a related table. The related table do have only one record with base information for the entire database. The related table is connected with use of the "X" mark ---------X----------- so data is valid for every record in the related second "big" table with many records. The data for the search script has to be looked up in that particular "one" record of the related base information field, and to be used for searching into the second table. I fail to see why his solution won't work? Or is it because the relationship to 'data' is broken while in find mode? If so, simply push the 'data' into a global before going into find mode. |
#6
| |||
| |||
|
| 42 wrote: mail.to.me (AT) fotograaf (DOT) invalid says... audleman (AT) quasika (DOT) net wrote: These are common confusions with FM7. Here are your answers. 1. The 'Specify Found Request' dialog box isn't extremely useful, as you can only input a set value. Instead, do the following in your script: Enter Find Mode[] SetField[A, 'data'] PerformFind[] Thanks for the answer, but onfortunalety it is not the answer for my my question. But looking your steps maybey you bring me to another thought, I have to try later these days (less time now). What I need is that the 'data' in your "SetField [A, 'data']" step is taken from the contents of a field from a related table. The related table do have only one record with base information for the entire database. The related table is connected with use of the "X" mark ---------X----------- so data is valid for every record in the related second "big" table with many records. The data for the search script has to be looked up in that particular "one" record of the related base information field, and to be used for searching into the second table. I fail to see why his solution won't work? Or is it because the relationship to 'data' is broken while in find mode? If so, simply push the 'data' into a global before going into find mode. Sorry if my understanding is not as good. That solution is searching for "data". That is not my problem. The point is, how to get a copy of the contents of a field into the search find "string" within a script, to do a search in the other table. For practical use (scripts are more complecated to edit each time) I don't want to fill in a search "text" within a scrip each time, because I have to change many times the search criteria. The solution I want to use is make use of a table where I can fill in the search values. Scripts has to look into that table, in such a way scripts pick up those values, and use it in the search mode to another table. I come back later (still not very much time these days). -- Vr.groet - regards, Léon Obers Reacties per mail, vervang "invalid" door "cc" in het adres. Reactions by mail, exchange "invalid" by "cc" within address. |
#7
| |||
| |||
|
|
You may create a global field GF, and show a layout with this field. The user will then fill GF will the proper search data he wants. A button nearby will launch the search script : Enter Find Mode[] SetField[A, GF] PerformFind[] Is this answering your question ? |
#8
| |||
| |||
|
| Remi-Noel Menegaux wrote: You may create a global field GF, and show a layout with this field. The user will then fill GF will the proper search data he wants. A button nearby will launch the search script : Enter Find Mode[] SetField[A, GF] PerformFind[] Is this answering your question ? Well, not exactly. But maybe we come close. For each of my customers I make an own database file. I want to change basic database settings for each of these customers (schools --> I am a school photographer), once. |
#9
| |||
| |||
|
|
Sorry if my understanding is not as good. That solution is searching for "data". That is not my problem. The point is, how to get a copy of the contents of a field into the search find "string" within a script, to do a search in the other table. |
#10
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |