Jump to content

Peter Wagemans

Members
  • Content Count

    77
  • Joined

  • Last visited

  • Days Won

    1

Peter Wagemans last won the day on August 9 2018

Peter Wagemans had the most liked content!

Community Reputation

3 Neutral

About Peter Wagemans

  • Rank
    just passing through

Profile Information

  • Title
    developer
  • Gender
    Male
  • Location
    Belgium

Contact Methods

  • Website URL
    http://www.lesterius.com/

FileMaker Experience

  • Skill Level
    Expert
  • FM Application
    18

Platform Environment

  • OS Platform
    X-Platform
  • OS Version
    Catalina

FileMaker Partner

  • Membership
    FileMaker TechNet
    FileMaker Business Alliance
    FIleMaker Platinum Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for that Joost. Now that we know these are QuickFind issues with improperly or unsearchable related fields, we can now help FileMaker turn there Unknown Error message into something like “QuickFind Error. Some related fields on this layout cannot be used with QuickFind.”. They will be so happy when we bring them the news. Imagine making something, and having this weird error number from your search engine you just can’t get your finger on. I know I would be happy if someone told me.
  2. Hi Stephen - I initially thought this was a APFS thing, but trying it on a High Sierra VM, I saw the same behaviour. Windows does what is expected, and gives an error. Creating records, changing field definitions, saving a copy as you mention, exporting, everything continues to work. Even renaming your file in the Finder is possible, without any error. This is also a nice one: make a script, select the export records script step. FileMaker format, make sure you are in your file its directory and type in your current file name. FileMaker asks if it can replace your file name, and you click yes. Even though the script has not run yet, FileMaker just deleted your active file. The number of shenanigans you can pull doesn't seem to end.
  3. macOS Catalina. 1. Make a new file and save it to the desktop 2. While the file is open, move it to the trash 3. empty the trash The trash is emptied without any error. Weird. This does not seem right, in fact it seems VERY wrong. Can anybody reproduce?
  4. Good catch. Thanks. The error number in the linked article is completely different. But I suppose the cause of the error has been unknowingly taken away - I will follow FIleMaker's lead here and call this "Unknown Solution: 1001" 🙂. Probably a whole bunch of errors with QuickFind haven't been mapped to text strings yet. Looking at the linked article, it seems to me that the QuickFind engine is still going through a number of changes throughout the versions of server and client and have as different behaviour on both on them. Good to know, even though I do not expect to code QuickFinds in FMSE. QuickFind is very useable and therefore a great feature, but it still has a number of unresolved problems, which lead to this kind of trouble. In current (v18) behaviour it is not possible to disable QuickFind for all elements in your layout by "Select All -> Disable QuickFInd", if they are embedded within other objects, they are ignored. I know you can disable QuickFind in the layout properties, but my point here is that developers do not expect FileMaker to ignore those extra fields, and since they are buried into other objects, this is hard to debug, and causes all kinds of problems with QuickFind. Increasing the problem, QuickFind has no "default field properties" behaviour, which makes every newly added field to the layout enabled for QuickFind. Which makes way to many fields enabled for QuickFind, as most mortal developers forget to uncheck the box. That was a stupid comment. The OP said the QuickFInd behaves differently when the file was hosted ( by an FMS16 ) and that is not the same as a server side script, of course. It does maybe point to improvements and might work correctly when the file would be hosted by an FMS18.
  5. Hi Olger, No plug-ins, and as I mentioned, I could not reproduce it myself, so there is no way I can debug this. Just thought someone here would have a more intimate knowledge of Unknown Errors in FileMaker. Apparently and by definition, these things are just unknown errors, and should be accepted as one of the mysteries of life.
  6. Someone any idea why FileMaker does not know it's own error codes? This happened when a customer with FileMaker 18 is trying to perform a scripted QuickFind. I cannot reproduce it.
  7. Got it and tested. It works indeed. On both machines. The LicenseCert file must still be in the downloads folder. Still not indicated in the installer. Poor FileMaker. http://fmdl.filemaker.com/esd/fms_18.0.3.319.dmg
  8. The link in that mail has long expired, Wim. Of course your advice is excellent, but I wonder why I need a sales person for technical support, and why the article https://support.filemaker.com/s/article/FileMaker-and-macOS-Catalina-Compatibility?language=en_US is not mentioning this problem, while it is simply happening when you try to install FileMaker Server on a Catalina machine. We do a lot of new installs, and I'm sure some collegue of mine recently did a fresh license install somewhere. So I will probably get this fixed somehow today... But... why does FIleMaker not provide full installers? Why does the link expire? This is the nth time this is happening, everytime a new OS version comes out, the base installer does not work anymore, but there is no way to solve the problem .... without contacting a SALES person??? Iknow, i iknow iknow, calm down.... 🙂 -- peter Got a filemaker.com download link from a collegue, will post this when I'm done downloading, because it's not downloading really fast...
  9. I am having the same issue here. On 2 separate machines, one is as good as a clean install. Problem: I have 18.01 and updaters, but I need a 18.03 installer, which... FileMaker does not provide. How to handle this?
  10. I have some trouble with testing a project with iOS SDK v18. Yesterday evening I updated my iPad Pro to iOS 13.1, and now XCode acts quite weirdly. trouble starting the app when running from XCode with earlier version I could stop the XCode run, and still start up the created app on the iPhone. Doesn't work anymore. Can anyone confirm?
  11. I have put this project aside. I think it works well enough for smaller setups. Those with more servers should maybe consider a commercial product. WB was written in Xojo, and requires an MBS plug-in license. For those who are serious about continuing work on this, let me and/or Claus know in a PM. I think I will transfer my code to Claus and let him decide on all this. I am a full time FileMaker developer and should not engage into too many side projects, I learned from this in the past. A centralised service where all FileMaker Servers push information to, is one way to do things, but a model where JSON can be used to pull information and send commands using that same API, is a zero deployment one, and seems to have become the better way to do things. This was not yet available when we started the project. Of course not all features of WB are supported already by the Admin API, but this is a good reason for asking FileMaker about it. FileMaker is going for subscription based hosting, maybe the server will evolve more quickly when they get first hand experience with the problems encountered when hosting a lot of servers.
  12. This really triggered my curiosity and I fired up my old win7 VM where I still have a 5 version. Even there, I could not find any graphical interface (using the tab bar on top of the window) that would give me a way to set tab stops for text fields (vs text boxes). So... I clearly misremembered that this was an option before. This is from the html file the OP refers to (this is from the 12 help): Well... that settles it 🙂
  13. Thanks for the tip. My point is, that it used to be possible to put a field on the layout, and, still in layout mode, assign tab stops to that field, not using the info panel, but using the tab ruler above. As the OP indicates: Indeed, this thread started about a field, not a text box with merge fields. I understand the issue can get a bit confusing ... 🙂 You indicate that i am getting off topic, but I was just comparing the workarounds.
  14. Exactly my point. Merge fields are a pain to use with tab stops, because their name is most of the time way to long, and this interferes with a wysiwyg experience. I last experienced even that the little trick to make the text font really small between the brackets, is not working anymore.
  15. Thanks for this question Xochi. Even if this topic is 4 years old. I am missing that possibility as well, and before reading thi posts, I thought I was misremembering how things used to work. . In the end I abandonded using tab stops and used fields, because this is very hard to make and maintain if you do not see what you are doing. Since I am currently working on a list layout, this multiplies the number of objects on the layout by 7. Which is not a good thing.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.