2 pointsThere exist several variations of the CSV format. The variation that Filemaker uses encloses all fields in double quotes. This allows exporting fields that contain commas, carriage returns and double quotes. According to the RFC 4180 specification: Any field may be quoted (with double quotes). Fields containing a line-break, double-quote or commas should be quoted. (If they are not, the file will likely be impossible to process correctly.) If double-quotes are used to enclose fields, then a double-quote must be represented by two double-quote characters. It should be noted that Filemaker's implementation does not fully conform to these requirements (or perhaps better put, it exceeds them) because it converts in-field carriage returns to vertical tabs, for no good reason. You need to create your own. The available methods depend on the version in use - see: https://fmforums.com/topic/106027-need-to-export-a-text-file-with-each-field-on-a-separate-line/?do=findComment&comment=479210 If you're indeed using version 11, then XML/XSLT is your only option - unless your target application can read UTF-16 encoded files. If it does, you can have a script write the CSV into a global text field, then export the field's content. Or, if you're willing to limit yourself to the Mac platform, you could use AppleScript to create the file (you could probably use OS-level scripting in Windows, too - but then you would have to put in twice the work). -- P.S. Your profile says version 11 on Catalina; I believe that's a very unstable combination. PP.S. What's up with the title?
1 pointA date field must contain a date - that is a specific day between January 1, 0001 and December 31, 4000. Otherwise it will contain invalid data that you won't be able to use for anything. To allow your users to enter partial dates, consider using a set of 3 number fields - day, month and year - for each date. Then use calculation fields to produce actual dates for find purposes. For example, for an entry of 1674 (with no month or day) into the Date1 set of fields, calculate the date of January 1, 1674 and for an entry of 9 and 1809 (with no day) into the Date2 set, calculate the date of September 30, 1809. Another option is to use a text field for the entry, but then you and your users must have an agreed convention for entering partial dates, otherwise you won't be able to parse the entries.
1 pointI am afraid you've lost me at this point. If it's possible to assign an item to a spot automatically, then why can't be dynamic? Of course, you can always number (or renumber) items by script (with the usual caveat regarding record locking).
1 pointJust installed FMS 9, (previously had from FMS 8). I am trying to access FMServer_Sample.fp7 in Safari 3.0.4. via the PHP test from the FileMaker Server 9 Technology Tests. I am getting the following error: Safari can’t open the page. Safari could not open the page “http://192.168.X.X/fmi-test/phptest.php?lang=en&server=.local” because the server stopped responding I am trying to access from a local machine. On the XServe that hosts the FMS 9 databases, Web services show as being enabled. In the FileMaker PHP Site Assistant I also get the error, "Connection failed. Please check server address. I can access FileMaker Server Admin console and it shows FMServer_Sample.fp7 as being enabled for PHP. I think this is actually a web server issue. How can I test the XServe web server? Thanks I am very new to php etc.
This leaderboard is set to Los Angeles/GMT-07:00