• Content count

  • Joined

  • Last visited

  • Days Won


artvault last won the day on January 28 2016

artvault had the most liked content!

Community Reputation

6 Neutral

About artvault

  • Rank

Profile Information

  • Gender
  • Location

Contact Methods

  • Website URL

FIleMaker Profile

  • FM Application
    14 Advanced
  • Platform
    Cross Platform
  • Certification
  • Membership
    FileMaker Business Alliance

Recent Profile Visitors

2,949 profile views
  1. That's exactly the sample file that I created for this thread and added above... :-) BUT it doesn't solve the problem with the order of the entries. FileMaker re-sorts alphabetically. And that was the actual question of the poster.
  2. See file attached... The idea is that you script the sorting action, memorize the record before the sort command and restore it through a relationship afterwards. You would have to test this against your scenario though, because I'm suspecting that other factors are interfering. I say this, because FileMaker generally stays on the same record, even when sorting. In short, I would have to know more about your exact setup...
  3. I removed my comment because I did not read your question carefully... sorry, I don't know of any solution for the sorting problem. In your scenario that works only in combination custom value lists, I think. Though you could capitalize "ALL" and such values to make them stand out at least?
  4. Thank you all for trying to help! I have taken the time today to separate all of the functionality that's related to this question and put it in a (new) sample file. I realize that the solution might consist of a work-around of sorts, so it's important to have the context. In the file attached you can see an attempt to emulate FileMaker "native" find mode within a user's UI (does not require visibility of status bar). A crucial part of this workflow is the insertion of search operators. Most search operators are not problematic. You can insert them by means of script without any issues. The problem exists with > or < operators. Filemaker immediately complains about "invalid find criteria". When wrapped in quotation marks, these are inserted into the field without any error messages. The challenge then is (that's what this thread was originally about) to remove the quotes. Unless there is a better way.... altogether? PS: use the "Enter Find Mode" button to get started - the rest should be obvious.
  5. Sorry, my bad, should be a backslash (FM automatically converts """" to "\""). I'll fix it. I don't think I should be working that late... I created a new file, same technique (supposedly), and it works! Sorry for taking up your time. I'm posting the sample file. Maybe this will be helpful to someone. Just FYI: I'm not going totally crazy. Luckily! Where it FAILS is in Find Mode. In Browse Mode it works like charm. So that might very well be impossible to solve. I'm am curious to why this is the case though...
  6. First thing I tried, not working, see original post.
  7. Believe it or not, this is actually it: "<" From that I need to remove quotation marks, so that I simply wind up with < in the field. Seems simple...
  8. Thank you Lee! "\<" returns \< Ok, then I just have to find a way to remove the backslash... LOL
  9. For your switch from FMS 13 to FMS 14 you should definitely you use the uninstaller for FMS 13, then do an install for FMS 14. As part of this procedure the correct Java version for will be installed (could be part of the problem). However, I would recommend to follow FileMaker's own recommendation and posts above: do a clean install of OS X first with NO SERVER. Current OS X Servers are no longer compatible with current FMS.
  10. There is a technique for pop-over buttons that are not attached to a specific button. It's described here: From within your first pop-over button you could use the GoToObject script step to open the second pop-over. Then use OnObjectExit to restore the first one. This would be a switching between two pop-over buttons though, nothing layered. Come to think of it, you could do that with two normal pop-over buttons too... :-| HOWEVER, with method above, a transparent pop-over area stretching your entire screen, you could probably "fake" a second layer to your objects placed within by help of show/hide and conditional formatting...
  11. I'm struggling to remove quotation marks from a symbol/operator such as this: "<" I have tried Substitute (Text; "\""; ""), as well as Brian Dunning's custom function RemoveSmartQuotes (text). Both works in the field of question perfectly with normal text, such as {hello "world"} ends up being {hello world}, but ho matter what I run "<" through, the quotation marks remain untouched. Any ideas?
  12. Oh! I was not aware of that. Thank you for pointing it out. So 100 connections is the new "unlimited" which is now officially available for purchase. Makes sense.
  13. Thank you for clarifying. I thought it had something to do with security concerns in relation to deep linking or other issues. PS: 100 connections is really a question of marketing and licensing. And I'm not too happy about it, because, combined with the recent price hikes, it makes "unlimited" WebDirect pretty much unaffordable.
  14. Your explanation makes me feel dimm in the best way possible. It didn't occur to me that refreshing the object (in this case the bar) would return it into its original state, which has the active segment highlighted. So simple. Brilliant.
  15. @Mark Scott - thank you for the tip! Fantastic article indeed. Very informative. Too bad about the icon limitation...