Korky

Here is one way to check on which memberships are due for renewal. It involves creating a script which, as a beginner, you may find a bit daunting. You may also wish to tackle this in a copy of your database rather than the original until you are confident you've got it right. I presume you already have an Expiry Date field, so first you need to create a new text field called "Expiry Flag"and place it on your selected layout.Now, in Scriptmaker, recreate the following script:

Check the FilemakerPro Help "Replacing the Contents of a Field".

Disregard the above. It's too clumsy. The attached file uses Portals as suggested by Oldsneekers.It's also much easier to create. Containerfieldsample.zip

Forgot to mention: when you open the file select New window then choose layout "Table".

Have a look at the attached file. It might give you a start. PictureButton.zip

The penny had already dropped, but thanks for responding.

I've solved the problem. I'd forgotten that you need to use a global value in Find Mode.Everything works now.

The actual execution of the Find is not the issue. It is that the script fails after Find mode is entered.I mentioned in an earlier post that the Paste (as well as Set Field)step will not work either. My script follows the pattern of the example submitted by "Enthusiast" above except for the omission of the Perform Find step.No one has faulted that. If you are using Set Field in Find Mode, what values are you setting if not a field content or based on a Field?

The script was amended accordingly.

Sorry but I pressed "Go" to soon. Here's the file. I just created it a few minutes ago as a test. It has two text fields and the script is simply; Enter Find Mode Set Field(Field 2;Field 1) The script pauses in Find Mode. I have also attempted the Paste step with equal lack of success. Findscript.zip

I don't know about a genie making your "Finds" work, but a gremlin is at work with me. I have run the same script in v5.5, and it doesn't work their either. In Dev7 I have run the debugger and no step will function after "Enter Find Mode" (the various buttons are greyed out).

I'm trying to achieve exactly the same as Jarvis and the fact seems to be that "Set Field" does not work in Find mode (in Dev 7). I have used it many times in previous versions, but cannot get it to work now.When Fenton's script is run an error dialog appears saying that there are no search criteria. What's to be done?

Here is a sample file to illustrate my previous post Options.zip

Whether you do this as a flat file solution or using a related Line Items file, there is still the problem of getting conventional checkboxes to work as you visualise. The way I got round a similar problem was to define a "Quantity" field and to fake a checkbox. This I did by formatting the Quantity field as Boolean and showing non-zeroes as "X" and zeroes as null. I then formatted the field as a button to run a setfield script using a Case step to toggle between 1 and 0. A calc field "Extension" stores the result of Quantity*Price. Prices are in Global Fields. In a flat file solution you have to define a set of fields and a script for each option.

I infer that you have a time field and a text field (into which you type) and that they are concatenated in a calculated field. Instead of using a calculated field, try creating a text block and lay a second instance of your time field on top in the upper left.To the right of time field, but still within the text box, insert a second instance of your text field as a Merge field (CTRL+M). You can format the time field as you desire. Type directly into the original text field and the text block should look like the calculated field you originally conceived.

Sorry,misunderstood the question!

The easiest way to achieve this is by creating a summary report. First create a new summary field "Locsum" (or whatever).Define this as a count of your "Location" field when sorted by "Location". Now create a new blank layout "Locations"; delete the body part and add a sub-summary part. Into the latter drag the "Locations" field and the new field "Locsum". *Change into preview mode, make sure you are in "Show All Records" and sort the records by "Location". Your report will read like LA 120 NY 300 etc Each time you want to view the report just repeat from * above.

I suspect that the answer to your problem is extremely simple. It's the question I can't understand. You seem to be saying that you want to go to each record in turn, grab a value from a particular field, then place that value in another field. This doesn't make sense. Can you explain a bit more please.

Another way of dealing with this would be to use the "Omit Record" step instead of delete. Your script would go like this:- Go to Record/request [first] Loop If [<<condition for deleting record>>] Omit record Else Go to record/request[next][exit after last] End If End loop Show Omitted Delete All Records This way you should avoid getting into an endless loop.

Create a new Filemaker database with 1 field. This can be anything. Create the "send message script" and make it the startup script in Preferences. Schedule this file for 7.00am in Tasks (in the Windows folder). Each day the file will open and the script will perform. Ensure that the file is closed either manually or by a script step. I think I got this answer from this forum some time ago.

When you click on either of the "Source" Tabs on the respective layouts FMPro performs a "Find" script. In order to find records within the found set you need to modify the last Find by adding another criterion. Thus the script underlying your Magnifying glass button would look like this:- Modify Last Find Go to Field["Recipe Title] When this script is run FMpro enters Find View with the Source Field already filled in. You enter data into the Recipe field and then click Find. You are actally running an "AND" request. Change your "Find All" buttons to run the same scripts as the "Source" Tabs. Problems with this approach are:- 1)If yo do a manual Find using the menu, this will be the last find and is the one that would be modified. This could produce strange results. 2) You couldn't allow for errors in the way that you have. I attach your file amended as above.

FM Pro has only one level of relationship. Your relationship heirarchy appears to be Purchases-Requisitions-Products. The top level, Purchases- Requisitions will not enable you to display fields from the second level, Requisitions-Products (as you have discovered). You must create calculated fields in Requisitions which follow the pattern Requisitions Description=:: Products Description. Do this for each of the Products fields you want to display in Purchases and you can then display the new fields in your purchase orders.

You can easily limit the number of characters in a field in v5.5 by validating the field and selecting the appropriate option. In earlier versions use validation by calculation with the following:- Length(Zip) <= 5

Check your calculation again.You show the field in the current file as"Student::Resident. The "::" suggests you have selected a related file,not the current file. It should just read If(Resident="yes" etc.

I presume you are storing the user name in a text field and that this was achieved using 'set field'. If so make the calculation read something like; Set Field,User History,User History&^&Current UserID [^=Carriage return] All this does is add a carriage return and the name of the new user to the existing data.