Lord HellFire

You're right... I've edited my previous post to reflect this.

[color:gray]My own solution to the problem... I found a way. I'm not proud and it gives extra work in making the scripts do the correct work, but I did the following. I have a repeating field with 50 repeats. I need to be able to search the first repeating field only, which apparently will not work as the search request searches all repeats when 1 is specified. Instead I used the 50th repeat field as the first. Insert the field to the layout, set it to show only repeats "50 to 50". This will show only the 50th field as the first line. Copy the field and set the new field to show repeats 1 to 49. This enables me to use field 50 as the first field. I had to adapt all the scripts to reflect this, however. A lot of extra work to make them consider the 50th field as the first. But it works... Maybe Filemaker should be forced to consider repeat 0 as all the repeating fields, so repeat 1 could refer to that field alone. Otherwise Filemaker is great Well.. Maybe I'm not really as smart as I thought I was. I assumed it would work. It doesn't. Repeating fields act as one field, when searching. The only option is to have a seperate field to use for searching, which hold a copy of the data (probably through a calculation to keep the data updated) Once again, I assumed that will work. Prove me wrong. It's not hard. [color:brown]I need repeating fields, as they make it MUCH easier to create the database. If I had to create one field for each needed field, I'd have to create hundreds of fields, instead of just 15 repeating. (50 repetitions each). I'd also have to specify EACH field in the calculations, as I still have not found a way to calculate a fields name, which can be used to specify a field. The SET FIELD option in scripts would be a killer to create, if I could not use repetitions. (hides the long list of wants and needs, which probably tell more about my inability concerning databases, than filemakers shortcomings)

Hi I've attached a file to show how I solved that problem in my own database. Only my database shows post codes and uses a check box field to show/hide them by country. It is also possible to add new post codes directly in the portal. I'm afraid I do not have time to explain how I created it, but mess around with it and you'll learn If not, I may have time later to explain. Enjoy. test.zip

Hi My database is a project database, where a repeating field is used for all the individual parts of the project and the first field is basically used as the overall status, except when there are more than one part in the project. A project with only one part uses just the first field. A project with 10 parts uses 10 of the repeating fields. Where the first is used as overall status. Problem is when searching for open and closed projects. A project can have closed parts, but still be open, which means the first field can be open, while some or all of the parts are closed. I have a script, which is supposed to show only open projects. It does so by omitting all projects, which contain the "closed" parts. Problem is that I cannot use ONLY repetition 1 to search in. I can specify any other repetition where it only searches that one, but when 1 is specified (which is default), it searches through all the repeating fields. If there any way to search ONLY the first repetition in a repeating field?

One more feature, which may help convince them: PDF generation is simple and easy. I don't know if you need to generate PDF's from any of your databases, but that's a feature I've been missing since day one. FINALLY the 8 incorporates this. I could make it print PDF's in v7, but I could not set any specific settings and had to supply filename myself for each record and click PRINT and stuff, since all I could do was call the PRINT dialog with the scripts. Now all I have to do is click a button and it prints PDF's for all the paychecks of the employees. Simple and timesaving. With a little more scripting, I could probably also make it email the paychecks aswell. Also valuelists pop up instantly (annoyed me incessantly in 6 and 7 on the PC)and the calendar feature is very nice. The $ and $$variables, which enable scripts to return values is very nice. I still have a shitload of nifty features I'd like to have included in the next release, but the 8 version certainly silenced many angry voices in me : (still some left, but many cried out in happiness and were then silent) It'd be a waste of good money to upgrade to 7 and then later upgrade to 8, when 8 has 90% of the features you need and 7 only has 50%... why not just wait for version 15 then? - Lord HellFire

Get the new version 8. The problem has been fixed there and new features have been added. -Lord HellFire

I'm basically just a rookie in designing databases and have only a rudimentary understanding of how databases work. I still don't quite understand all the concepts of the relationship parts. The database I'm building/improving upon consists of several interworking databases (5-7 or somewhere around there) and each is one file. Keeping them in their own files serves some advantages. Having one big file would create a single point of failure and thats not a good thing. Your calculation for creating the list of languages is better and simpler than mine. I still have a lot of things to work on. This self-updating list of translators, based on the two chriterias (from and to language), has been a (insert profanity here) for the last half year. I couldn't make it work without using a script and a button to update the list. I finally worked it out after installing the new Filemaker Pro 8. Then tried it in the 7 and it still worked. I felt stupid, because I didn't figure out how it worked half a year ago, especially when the solution was as simple as it was. I tried looking for solutions online as to how it could be done, but found no real answer that could help me. Not even in this forum. I may simply have been looking in the wrong places or simply overlooked the posts that contained the right answers. Anyway... I still have a lot of work to do on the database Some of the new features in Pro 8 is something I've been missing for quite some time. Proper PDF generation is one, the quicker updating lists and the arrow for showing the lists. Stuff I'm still missing: Easier script-editing (notepad style would be nice) Control over files on the harddrive. - Our company deals with a lot of different files and it would be nice if the database could, at least, keep an eye on where the files are located. It doesn't have to have a copy of the file in the database (10 gigs of files is a bit much for a database to hold), but the ability to move directories or files would be nice, so once a project is complete, it could move the files to a storage folder, so only active projects are stored in the "active" folder. Once I get through all the new features in Pro 8, I think I'll update my "list-o-things-filemaker-should-be-able-to-do" and get it sent in for the developers. Filemaker is the best and easiest database program I've come across. There are still just a lot of nifty features missing. And I still need to learn how to make good databases : -Lord HellFire

Hi I've been struggling with creating a dynamic value list, based on selected options. The short story is that I've been trying to create a database, that list available translators, based on their language skills and what language the project is for. I finally managed to create this list, which updates as soon as I change the from/to languages. For this purpose, I've created two files/databases. 1: Employee database It contains information about the employees. The ID field is the short name for the employee. It also contains 10 x 2 Pulldown-menus for selecting from and to languages. (10 possible language combinations). An extra field is created; THELIST, which is a calculation, that continously generates a list of these combinations using a calculation: FROMLANGUAGE1 & " to " & TOLANGUAGE1 & ####here is the next-line tag #### FROMLANGUAGE2 & " to " & TOLANGUAGE2 & ####here is the next-line tag #### and so on up to 12. This list looks like this: -- Danish to English French to Swedish -- and so on, based on the from/to fields. I did put more into the calculation to prevent empty fields from showing up in the list, but never mind that here. This THELIST field is important in the search for the correct translators for projects. 2: Project database. This database contains all the informations about the projects. I created a FROM and a TO field, where I select the languages. Then I created a third field COMBINED, which is a calculation: FROM & " to " & TO This calculation creates a line, which must match the content of the list in the employee file. Under RELATIONS in this database, you create a relation between the PROJECT::COMBINED field and the EMPLOYEE::THELIST The relation must be a = relation. Then you create a value list TRANSLATORS. USE VALUES FROM FIELD Select the EMPLOYEE database and the ID field. Set it to INCLUDE ONLY RELATED VALUES starting from the PROJECT database. Use this valuelist in the PROJECT database. I've attached a sample database to show this concept. (2 files) The fields does not have the same names as I mentioned here, as I stripped my existing database down to have only the conceptual fields remaining. This can also be created in one database using multiple tables. Hope this helps some of you out there, who are trying as he#¤"#¤ to make something like this work. -Lord HellFire project-employee.zip

Hi I'm trying to make Filemaker perform a find on text of a specific color, so it can omit the records it finds with text in a given color. Current script: ---- * [color:red]Show All Records * [color:red]Enter Find Mode [Pause] [color:brown]//Search text is entered here// * [color:red]Perform Find * [color:red]Go To Record/Request/Page [First] * [color:red]Loop * [color:green]Go to Field [database::fieldname] * [color:green]If [Get ( ActiveFieldContents ) = TextColor ( database::fieldname ; RGB ( 0 ; 255 ; 0 ))] [color:brown]//should check if text is green// * [color:blue]Omit Record * [color:green]Else * [color:blue]Go To Record/Request/Page [Next;Exit after Last] * [color:green]End If * [color:green]Exit Loop If [Get ( FoundCount ) = "0" ) [color:brown]//To prevent it looping forever, if all records have been omitted// * [color:red]End Loop It doesn't check if the color is correct; it just checks if the text is the same. I want it to check the color. I can't find any other functions, that compare the color of the text or extract the color information from text. Help? Kind Regards Lord HellFire 'Eternal Life or Your Money Back

Another possibility for creating a value list is this Create a COMPANY file -Create x amount of ITEMNAMEFIELDs -Create a field COMPANYNAME Create a TEMPFILE. -Create a field for each ITEMNAMEFIELD in the COMPANY file. (if there are 10 ITEMNAMEFIELDs in the COMPANY file, create 10 ITEMNAMEFIELDs in the TEMPFILE. ----TYPE: Text ----Set to Lookup. Field 1 looksup COMPANY::ITEMNAMEFIELD 01, field 2 looksup field 2 in company and so on. -Create a field COMPANYNAME. ----TYPE: Text ----Global Field -------You must create a relation between this field and the COMPANYNAME field in the COMPANY file. -Create a field VALUELIST ----TYPE: Calculation ----Always evaluate ----Minimal Indexing ----Calculation: If(Get ( RecordNumber )=1;ITEMNAMEFIELD 01; If(Get ( RecordNumber )=2;ITEMNAMEFIELD 02; If(Get ( RecordNumber )=3;ITEMNAMEFIELD 03; If(Get ( RecordNumber )=4;ITEMNAMEFIELD 04; If(Get ( RecordNumber )=5;ITEMNAMEFIELD 05; If(Get ( RecordNumber )=6;ITEMNAMEFIELD 06; If(Get ( RecordNumber )=7;ITEMNAMEFIELD 07; If(Get ( RecordNumber )=8;ITEMNAMEFIELD 08; If(Get ( RecordNumber )=9;ITEMNAMEFIELD 09; If(Get ( RecordNumber )=10;ITEMNAMEFIELD 10;"ERROR")))))))))) Now create 10 records. Now create a script named "RELOOKUP" in the TEMPFILE. -RELOOKUP FIELD [NO DIALOG;TEMPFILE::COMPANYNAME] Then create a script named "UPDATE ITEMLIST" in the file you wish to create the valuelist in. -SET FIELD [TEMPFILE::COMPANYNAME; valuelistfile::COMPANYNAME] -PERFORM SCRIPT ["RELOOKUP" from file: "TEMPFILE"] Create a valuelist pointing to TEMPFILE::VALUELIST Now create a button next to the itemlistfield, which runs the script "UPDATE ITEMLIST". When you run the script, it transfers the companyname to the temp file. Then runs the script "RELOOKUP" which lookup the list of items for that company into the temp file. The Valuelist field in each record uses the data which was looked up. Record 1 contains the item name from ITEMNAMEFIELD 01, record 2 from 02 and so on. The valuelist now becomes populated with all the items, because it uses all 10 records from the temp file, each containing a specific item. Hope that helps too.