Rigsby

The Good, the Bad and the Ugly! The Good You need to develop your solution as a

I streamlined it a bit by using letters instead of numbers for the Choose(Position( part, as it had problems with more than 10 words otherwise. But this was easy to do with a substitute("26","Z") etc. command. This way I can sort up to 26 values without having to play with the position.... -1 command. 26 is more than enough for my needs, but I'm sure there would be a way to get more. Very streamline, very effective... I'm still facing lots of other problems, but this has really helped.

Coool!!! just what I needed! I've up-ed it to 25 field (words) and it works fine. Now I need to test it on the full 500,000 records. Thanks

"Crude" Yes, but it works..... And you're right it just gave me a very fresh idea that I think might work. I need to get this tested on my 500,000 records for speed, but I think you just gave me a push in the right direction. Thanks, and thanks again Rigsby

Thanks fort he Tipp, I

It is sometimes difficult to ask for help, and at the same time explain the sense of the full solution on is working on! I try to keep posts short and to the point so that those who might be able to help don

Maybe I'm stupid, but what exactly do you mean by "You need to stuff it inside a Evaluate( and remember to make before each " ...."

:-) I was just working on the value list idea! Thanks for the quick reply. The problem I'm having is that the ValueList field is not updating unless I change layouts or enter the field. However, I think I can get round that!

I have 25 separate fields containing different numbers and text values, but these are limited to 1 word per field: E.G: Txt1 =

You can export to any format and have Filemaker include field names as the first values in the file. The trick is to create a dummy (empty) record and set the field values in that record to the field name values. Then make sure you use sort criteria that guarantees that the dummy record is the first record in the set. Export the set, and you have the field names as the first entry in your text (or whatever) file. :-)

If the divider in the text field can be a comma, colon or semicolon, but these symbols can also occur where the text shouldn

The solutions here are all good, but the whole thing can be done in a much easier fashion. The difference is only where you choose to put your

There are several ways to do what you want! I would use the following: You have three fields: <OrigText> This is your original text field, and two calculating fields, <TextLeft> which takes the value before the , : or ; and <TextRight>, which takes the value after. The first step is to grab the text to the left of the symbol, however, it makes things easier if we firstly convert the possible symbols to a comma using the substitute command, and also remove this comma from the result using the substitute command, so: TextLeft = Trim(Substitute(Left( OrigText; Position( Substitute( Substitute(OrigText, ":", ","),";",","), ",", 0, 1)), ",", "")) So, for example, if in the field OrigText we had the value:

This can be done, but you need to re-think the structure of your database. What you need to do is store all your images in another file using a relationship between the two files, then when a user clicks on a link or a thumbnail in the main file, the second file can be brought to the front using go to related record steps. You can then use the window commands in script maker to resize both windows to suit your needs.

The reason the files close then open again is as said, because of relationships. To get around this, simply switch layouts. What I would recommend is a so-called farewell screen, saying goodbye to the user. Thus, there are no related fields or portals on the layout to trigger the files again. This will do it!